[gpfsug-discuss] Pool layoutMap option changes following GPFS upgrades

[Caron, Paul]

Hi,

Has anyone run into a situation where the layoutMap option for a pool changes from "scatter" to "cluster" following a GPFS software upgrade?  We recently upgraded a file system from 3.5.0.21, to 4.1.1.17, and finally to 4.2.3.6.  We noticed that the layoutMap option for two of our pools changed following the upgrades.  We didn't recreate the file system or any of the pools.  Further lab testing has revealed that the layoutMap option change actually occurred during the first upgrade to 4.1.1.17, and it was simply carried forward to 4.2.3.6.  We have a PMR open with IBM on this problem, but they have told us that layoutMap option changes are impossible for existing pools, and that a software upgrade couldn't do this.  I sent the results of my lab testing today, so I'm hoping to get a better response.

We would rather not have to recreate all the pools, but it is starting to look like that may be the only option to fix this.  Also, it's unclear if this could happen again during future upgrades.

Here's some additional background.

*         The "-j" option for the file system is "cluster"

*         We have a pretty small cluster; just 13 nodes

*         When reproducing the problem, we noted that the layoutMap option didn't change until the final node was upgraded

*         The layoutMap option changed before running the "mmchconfig release=LATEST" and "mmchfs <fs> -V full" commands, so those don't seem to be related to the problem

Thanks,

Paul C.
SIG


________________________________

IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20180323/181b0ac7/attachment.htm>