[gpfsug-discuss] mmapplypolicy not terminating properly?

Marc A Kaplan makaplan at us.ibm.com
Wed Apr 19 18:10:28 BST 2017


(Bryan B asked...)

Open a PMR.  The first response from me will be ...  Run the mmapplypolicy 
command again, except with additional option `-d 017` and collect output 
with something equivalent to  `2>&1  |  tee 
/tmp/save-all-command-output-here-to-be-passed-along-to-IBM-service `  If 
you are convinced that mmapplypolicy is "looping" or "hung" - wait another 
2 minutes, terminate, and then pass along the saved-all-command-output.

-d 017 will dump a lot of additional diagnostics -- If you want to narrow 
it by baby steps we could try  `-d 03` first and see if there are enough 
clues in that.

To answer two of your questions: 
1. mmapplypolicy does not follow symlinks, so no "infinite loop" possible 
with symlinks.

2a. loops in directory are file system bugs in GPFS, (in fact in any 
posixish file system), (mm)fsck!
2b. mmapplypolicy does impose a limit on total length of pathnames, so 
even if there is a loop in the directory, mmapplypolicy will "trim" the 
directory walk.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20170419/dffc5201/attachment.htm>


More information about the gpfsug-discuss mailing list