(Somewhat educated guess.) Somehow a previous incarnation of the mmfsd daemon was killed, but left its shared segment laying about. When GPFS is restarted, it discovers the old segment and deallocates it, etc, etc... Then the safest, easiest thing to do after going down that error recover path is to quit and (re)start GPFS as if none of that ever happened. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20190523/8e8465fe/attachment.html>