<font size=2 face="sans-serif">Yes, you can do this. In release
4.1.1 you can write SET POOL 'x' ACTION(setXattr(...)) FOR
FILESET(...) WHERE ...</font>
<br><font size=2 face="sans-serif">which looks nicer to some people than
WHERE ( ... ) AND setXattr(...)<br>
</font>
<br><font size=2 face="sans-serif">Answers:</font>
<br>
<br><font size=2 face="sans-serif">(1) No need to quiesce. As the
new policy propagates, nodes begin using it. So there can be a transition
time when node A may be using the new policy but Node B has not started</font>
<br><font size=2 face="sans-serif">using it yet. If that is undesirable,
you can quiesce. </font>
<br>
<br><font size=2 face="sans-serif">(2) Yes, 1MB is a limit on the total
size in bytes of your policy rules. Do you have a real need for more?
Would you please show us such a scenario? Beware that policy rules
take some cpu cycles to evaluate... So if for example, if you had
several thousand SET POOL rules, you might notice some impact to file creation
time.</font>
<br>
<br><font size=2 face="sans-serif">--marc of GPFS</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Luke Raimbach <Luke.Raimbach@crick.ac.uk></font>
<br><font size=2 face="Calibri"> ... </font>
<br><font size=2 face="Calibri">RULE 'RDMTEST'</font>
<br><font size=2 face="Calibri"> SET POOL 'instruments\u2019</font>
<br><font size=2 face="Calibri"> FOR FILESET</font>
<br><font size=2 face="Calibri">('%GPFSRDM%10.01013%RDM%0ab34906-5357-4ca0-9d19-a470943db30a%RDM%8fc2395d-64c0-4ebd-8c71-0d2d34b3c1c0')</font>
<br><font size=2 face="Calibri"> WHERE SetXattr</font>
<br><font size=2 face="Calibri">('user.rdm.parent','0ab34906-5357-4ca0-9d19-a470943db30a')</font>
<br><font size=2 face="Calibri"> AND SetXattr</font>
<br><font size=2 face="Calibri">
('user.rdm.ingestor','8fc2395d-64c0-4ebd-8c71-0d2d34b3c1c0')</font>
<br><font size=2 face="Calibri">RULE 'DEFAULT' SET POOL 'data'</font>
<br><font size=2 face="Calibri"> ...</font>
<br><font size=2 face="Calibri">(1) When I install a placement policy into
the file system, does the file system need to quiesce? My suspicion is
yes, because the policy needs to be consistent on all nodes performing
I/O, but I may be wrong.</font>
<br><font size=2 face="Calibri"> ...</font>
<br><font size=2 face="Calibri">(2) What is the specific limitation for
having a policy placement file no larger than 1MB?</font>
<br><font size=2 face="Calibri"> ...</font>
<p>