Hi Marc, Alex, all,
Thank you for the responses. To answer Alex’s questions first … the full
command line I used (except for some stuff I’m redacting but you don’t need the
exact details anyway) was:
/usr/lpp/mmfs/bin/mmapplypolicy gpfs23 -A 75 -a 4 -g -I yes -L 1 -P
Oops... If you want to see the list of what would be migrated '-I test
-L 2' If you want to migrate and see each file migrated '-I yes -L 2'
I don't recommend -L 4 or higher, unless you want to see the files that do
not match your rules.
-L 3 will show you all the files that match the
Kevin,
1. Running with both fairly simple rules so that you migrate "in both
directions" is fine. It was designed to do that!
2. Glad you understand the logic of "rules hit" vs "files chosen".
3. To begin to understand "what the hxxx is going on" (as our fearless
leader liked to say before
Hi Kevin,
IMHO, safe to just run it again.
You can also run it with '-I test -L 6' again and look through the
output. But I don't think you can "break" anything by having it scan
and/or move data.
Can you post the full command line that you use to run it?
The behavior you describe is odd;
Hi Marc,
I do understand what you’re saying about mmapplypolicy deciding it only needed
to move ~1.8 million files to fill the capacity pool to ~98% full. However, it
is now more than 24 hours since the mmapplypolicy finished “successfully” and:
Disks in storage pool: gpfs23capacity (Maximum
