[gpfsug-discuss] Well, this is the pits...

[Buterbaugh, Kevin L]

Hi All,

Another one of those, “I can open a PMR if I need to” type questions…

We are in the process of combining two large GPFS filesystems into one new filesystem (for various reasons I won’t get into here).  Therefore, I’m doing a lot of mmrestripe’s, mmdeldisk’s, and mmadddisk’s.

Yesterday I did an “mmrestripefs <old fs> -r -N <my 8 NSD servers>” (after suspending a disk, of course).  Worked like it should.

Today I did a “mmrestripefs <new fs> -b -P capacity -N <those same 8 NSD servers>” and got:

mmrestripefs: The total number of PIT worker threads of all participating nodes has been exceeded to safely restripe the file system.  The total number of PIT worker threads, which is the sum of pitWorkerThreadsPerNode of the participating nodes, cannot exceed 31.  Reissue the command with a smaller set of participating nodes (-N option) and/or lower the pitWorkerThreadsPerNode configure setting.  By default the file system manager node is counted as a participating node.
mmrestripefs: Command failed. Examine previous error messages to determine cause.

So there must be some difference in how the “-r” and “-b” options calculate the number of PIT worker threads.  I did an “mmfsadm dump all | grep pitWorkerThreadsPerNode” on all 8 NSD servers and the filesystem manager node … they all say the same thing:

   pitWorkerThreadsPerNode 0

Hmmm, so 0 + 0 + 0 + 0 + 0 + 0 + 0 + 0 + 0 > 31?!?  I’m confused...

—
Kevin Buterbaugh - Senior System Administrator
Vanderbilt University - Advanced Computing Center for Research and Education
Kevin.Buterbaugh at vanderbilt.edu<mailto:Kevin.Buterbaugh at vanderbilt.edu> - (615)875-9633



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20170504/3e04d864/attachment-0001.htm>