<span style=" font-size:10pt;font-family:sans-serif">Migrate to a group
pool "repacks" the selected files over the pools that comprise
the group IN THE ORDER SPECIFIED UP TO THE SPECIFIED LIMIT for each pool.
To see this work, in your case, set a limit that is near the current
occupancy of pool 'ssd'.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">For example: </span><span style=" font-size:11pt;font-family:Calibri">RULE
\u2018gp\u2019 GROUP POOL \u2018gpool\u2019 is \u2018ssd\u2019 LIMIT(50) then \u2018disk1\u2019</span><span style=" font-size:10pt;font-family:sans-serif"><br></span><br><span style=" font-size:10pt;font-family:sans-serif">Notice the documentation
says the LIMIT defaults to 99.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">Also, if you've
run the same policy before and nothings changed much, then of course, there's
not going to be much "repacking" to be done, maybe not any.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">If the behaviour
still doesn't make sense to you, try testing on a tiny file system with
just a few small pools, sizing pools and files so that only a few files
will fit in a pool... If you build such a test scenario and that
still doesn't make sense, show us the example...</span><br><br><span style=" font-size:10pt;font-family:sans-serif">-----------------------------------</span><br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">From:
</span><span style=" font-size:9pt;font-family:sans-serif">"Powell
(US), Richard E" <Richard.E.Powell@boeing.com></span><br><br><br><span style=" font-size:11pt;font-family:Calibri">Hi all,</span><br><span style=" font-size:11pt;font-family:Calibri"> </span><br><span style=" font-size:11pt;font-family:Calibri">I\u2019m trying to use
the \u201cGROUP POOL\u201d feature for file migration with FILE_HEAT, similar to
one of the ilm sample scripts. The problem I\u2019m having is that it
seems to be identifying the candidates correctly but, anytime I use the
\u201cgroup pool\u201d name for the \u201cto pool\u201d, it only selects the first candidate
for migration. If I specify a single pool name for the \u201dto pool\u201d,
it selects multiple files as expected.</span><br><span style=" font-size:11pt;font-family:Calibri"> </span><br><span style=" font-size:11pt;font-family:Calibri">Here are the policy
rules I\u2019m using:</span><br><span style=" font-size:11pt;font-family:Calibri"> </span><br><span style=" font-size:11pt;font-family:Calibri">RULE \u2018gp\u2019 GROUP
POOL \u2018gpool\u2019 is \u2018ssd\u2019 then \u2018disk1\u2019</span><br><span style=" font-size:11pt;font-family:Calibri">RULE \u2018repack\u2019 MIGRATE
FROM POOL \u2018gpool\u2019 TO POOL \u2018gpool\u2019 WEIGHT(FILE_HEAT)</span><br><span style=" font-size:11pt;font-family:Calibri"> </span><br><span style=" font-size:11pt;font-family:Calibri">I\u2019m not sure if
I\u2019m misunderstanding something or if this is a real bug. I\u2019m just
wondering if anyone else has run into this issue?</span><br><span style=" font-size:11pt;font-family:Calibri"> </span><br><span style=" font-size:11pt;font-family:Calibri">I\u2019m running 4.2.3.8
on RHEL 6.</span><br><span style=" font-size:11pt;font-family:Calibri"> </span><br><span style=" font-size:11pt;font-family:Calibri">Thanks!</span><br><span style=" font-size:11pt;font-family:Calibri">Richard</span><br><BR>