[gpfsug-discuss] Failure Group

[Jan Finnerman Load]

Hi,

I have a customer with GPFS 3.4.0.11 on Windows @VMware with VMware Raw Device Mapping. They just ran in to an issue with adding some nsd disks.
They claim that their current file system’s nsddisks are specified with 4001 as the failure group. This is out of bounds, since the allowed range is –1>–—>4000.
So, when they now try to add some new disks with mmcrnsd, with 4001 specified, they get an error message.

Customer runs this command: mmcrnsd -F D:\slask\gpfs\gpfsdisk.txt
[Description: cid:image001.png at 01D18B5D.FFCEFE30]


His gpfsdisk.txt file looks like this.
[Description: cid:image002.png at 01D18B5D.FFCEFE30]


A listing of current disks show all as belonging to Failure group 4001
[Description: cid:image003.png at 01D18B5D.FFCEFE30]

So, Why can’t he choose failure group 4001 when the existing disks are member of that group ?
If he creates a disk in an other failure group, what’s the pros and cons with that ? I guess issues with replication not working as expected….

Brgds
///Jan

[cid:95049B1E-9581-4B5E-8878-5BC3F3371B27]
Jan Finnerman
Senior Technical consultant

[CertTiv_sm]

[cid:DB2EE70A-D139-4B15-B58C-5BD987D2FAB5]
Kista Science Tower
164 51 Kista
Mobil: +46 (0)70 631 66 26
Kontor: +46 (0)8 633 66 00/26
jan.finnerman at load.se<mailto:jan.finnerman at load.se>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160401/3cecd7e1/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: F1EE9474-7BCC-41E6-8237-D949E9DC35D3.png
Type: image/png
Size: 5565 bytes
Desc: F1EE9474-7BCC-41E6-8237-D949E9DC35D3.png
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160401/3cecd7e1/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: E895055E-B11B-47C3-BA29-E12D29D394FA.png
Type: image/png
Size: 8584 bytes
Desc: E895055E-B11B-47C3-BA29-E12D29D394FA.png
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160401/3cecd7e1/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CertPowerSystems_sm[1].png
Type: image/png
Size: 6664 bytes
Desc: CertPowerSystems_sm[1].png
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160401/3cecd7e1/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: B13E252A-3014-49AD-97EE-6E9B4D57A9F4.png
Type: image/png
Size: 3320 bytes
Desc: B13E252A-3014-49AD-97EE-6E9B4D57A9F4.png
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160401/3cecd7e1/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 7A01C40C-085E-430C-BA95-D4238AFE5602.png
Type: image/png
Size: 1648 bytes
Desc: 7A01C40C-085E-430C-BA95-D4238AFE5602.png
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160401/3cecd7e1/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 446525C9-567E-4B06-ACA0-34865B35B109.png
Type: image/png
Size: 6144 bytes
Desc: 446525C9-567E-4B06-ACA0-34865B35B109.png
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160401/3cecd7e1/attachment-0005.png>