Hi Kevin, I'm running policy migrations on Spectrum Scale 4.2.3, but I use mmapplypolicy to kick off the policy runs, not mmstartpolicy. Docs here (which I admit are not for your version of Spectrum Scale) state that mmstartpolicy is for internal GPFS use only: https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/General+Parallel+File+System+(GPFS)/page/Using+Policies
So if the above link is correct, I'd recommend switching to using mmapplypolicy, which handily comes with a man page, whereas mmstartpolicy doesn't and might have you fumbling around in the dark. As for the issue you're experiencing with adding a callback, it looks like the mmaddcallback command is catching the --single-instance flag as an argument for it, not as a parameter for the mmstartpolicy command. After looking at the documentation you've referenced, I suspect that there's a typo/omission in the command and it should have a trailing double quote (") on the end of the parms argument list, i.e.: mmaddcallback MIGRATION --command /usr/lpp/mmfs/bin/mmstartpolicy --event lowDiskSpace --parms "%eventName %fsName --single-instance" I'm not sure how we go about asking IBM to correct their documentation, but expect someone in the user group will have some idea. Regards, Pete Chase peter.ch...@metoffice.gov.uk -----Original Message----- From: gpfsug-discuss-boun...@spectrumscale.org <gpfsug-discuss-boun...@spectrumscale.org> On Behalf Of gpfsug-discuss-requ...@spectrumscale.org Sent: 06 August 2018 23:47 To: gpfsug-discuss@spectrumscale.org Subject: gpfsug-discuss Digest, Vol 79, Issue 21 Send gpfsug-discuss mailing list submissions to gpfsug-discuss@spectrumscale.org To subscribe or unsubscribe via the World Wide Web, visit http://gpfsug.org/mailman/listinfo/gpfsug-discuss or, via email, send a message with subject or body 'help' to gpfsug-discuss-requ...@spectrumscale.org You can reach the person managing the list at gpfsug-discuss-ow...@spectrumscale.org When replying, please edit your Subject line so it is more specific than "Re: Contents of gpfsug-discuss digest..." Today's Topics: 1. mmaddcallback documentation issue (Buterbaugh, Kevin L) 2. Re: mmaddcallback documentation issue (Eric Sperley) ---------------------------------------------------------------------- Message: 1 Date: Mon, 6 Aug 2018 21:42:54 +0000 From: "Buterbaugh, Kevin L" <kevin.buterba...@vanderbilt.edu> To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org> Subject: [gpfsug-discuss] mmaddcallback documentation issue Message-ID: <735f4275-191a-4363-b98c-1ea289292...@vanderbilt.edu> Content-Type: text/plain; charset="utf-8" Hi All, So I?m _still_ reading about and testing various policies for file placement and migration on our test cluster (which is now running GPFS 5). On page 392 of the GPFS 5.0.0 Administration Guide it says: To add a callback, run this command. The following command is on one line: mmaddcallback MIGRATION --command /usr/lpp/mmfs/bin/mmstartpolicy --event lowDiskSpace --parms "%eventName %fsName --single-instance The --single-instance flag is required to avoid running multiple migrations on the file system at the same time. However, trying to issue that command gives: mmaddcallback: Incorrect option: --single-instance And the man page for mmaddcallback doesn?t mention it or anything similar to it. Now my test cluster is running GPFS 5.0.1.1, so is this something that was added in GPFS 5.0.0 and then subsequently removed? I can?t find the GPFS 5.0.1 Administration Guide with a Google search. Thanks? Kevin ? Kevin Buterbaugh - Senior System Administrator Vanderbilt University - Advanced Computing Center for Research and Education kevin.buterba...@vanderbilt.edu<mailto:kevin.buterba...@vanderbilt.edu> - (615)875-9633 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://gpfsug.org/pipermail/gpfsug-discuss/attachments/20180806/d4348ee3/attachment-0001.html> ------------------------------ Message: 2 Date: Mon, 6 Aug 2018 15:46:39 -0700 From: "Eric Sperley" <espe...@us.ibm.com> To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org> Subject: Re: [gpfsug-discuss] mmaddcallback documentation issue Message-ID: <of2e0e1104.a39aa4c3-on002582e1.007d02c1-882582e1.007d1...@notes.na.collabserv.com> Content-Type: text/plain; charset="utf-8" See if this helps https://www.ibm.com/support/knowledgecenter/en/STXKQY_5.0.1/com.ibm.spectrum.scale.v5r01.doc/bl1adm_mmaddcallback.htm Best Regards, Eric Eric Sperley, PhD SDI Architect To improve is to change; to be perfect is IBM Systems to change often - - Winston Churchill espe...@us.ibm.com +15033088721 From: "Buterbaugh, Kevin L" <kevin.buterba...@vanderbilt.edu> To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org> Date: 08/06/2018 02:44 PM Subject: [gpfsug-discuss] mmaddcallback documentation issue Sent by: gpfsug-discuss-boun...@spectrumscale.org Hi All, So I?m _still_ reading about and testing various policies for file placement and migration on our test cluster (which is now running GPFS 5). On page 392 of the GPFS 5.0.0 Administration Guide it says: To add a callback, run this command. The following command is on one line: mmaddcallback MIGRATION --command /usr/lpp/mmfs/bin/mmstartpolicy --event lowDiskSpace --parms "%eventName %fsName --single-instance The --single-instance flag is required to avoid running multiple migrations on the file system at the same time. However, trying to issue that command gives: mmaddcallback: Incorrect option: --single-instance And the man page for mmaddcallback doesn?t mention it or anything similar to it. Now my test cluster is running GPFS 5.0.1.1, so is this something that was added in GPFS 5.0.0 and then subsequently removed? I can?t find the GPFS 5.0.1 Administration Guide with a Google search. Thanks? Kevin ? Kevin Buterbaugh - Senior System Administrator Vanderbilt University - Advanced Computing Center for Research and Education kevin.buterba...@vanderbilt.edu - (615)875-9633 _______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://gpfsug.org/pipermail/gpfsug-discuss/attachments/20180806/381f9169/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: 1A910265.gif Type: image/gif Size: 481 bytes Desc: not available URL: <http://gpfsug.org/pipermail/gpfsug-discuss/attachments/20180806/381f9169/attachment.gif> -------------- next part -------------- A non-text attachment was scrubbed... Name: ecblank.gif Type: image/gif Size: 45 bytes Desc: not available URL: <http://gpfsug.org/pipermail/gpfsug-discuss/attachments/20180806/381f9169/attachment-0001.gif> -------------- next part -------------- A non-text attachment was scrubbed... Name: 1A526482.gif Type: image/gif Size: 2322 bytes Desc: not available URL: <http://gpfsug.org/pipermail/gpfsug-discuss/attachments/20180806/381f9169/attachment-0002.gif> -------------- next part -------------- A non-text attachment was scrubbed... Name: graycol.gif Type: image/gif Size: 105 bytes Desc: not available URL: <http://gpfsug.org/pipermail/gpfsug-discuss/attachments/20180806/381f9169/attachment-0003.gif> ------------------------------ _______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss End of gpfsug-discuss Digest, Vol 79, Issue 21 ********************************************** _______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss