If by a wrong manipulation of your disks by the SAN team (which we just had), and on one your cluster’s node ,
when you type lspv, you’ve got no more labels on your NSD hdisks:

 # lspv
hdisk4          00f6af60810a2534                    rootvg          active
hdisk5          00f6af608efb31ce                    appsvg          active
hdisk0          none                                None
hdisk1          none                                None
hdisk3          none                                None
hdisk2          none                                None
hdisk6          none                                None
hdisk7          none                                None
hdisk8          none                                None
hdisk9          none                                None
hdisk10         none                                None
hdisk11         none                                None

Though NSDs are there, and GPFS is running fine :

 # mmlsnsd

 File system   Disk name    NSD servers
---------------------------------------------------------------------------
 gpfs_fs     gVNX0521_4303_100 node1,node2
 gpfs_fs     gVNX0521_4403_100 node1,node2
 gpfs_fs     gVNX0521_4503_100 node1,node2
 gpfs_fs     gVNX0521_4603_100 node1,node2
 gpfs_tiebreaker gVNX0521_4203_001 node1,node2

# mmlsmgr
file system      manager node
---------------- ------------------
gpfs_tiebreaker  10.10.10.1 (node1)
gpfs_fs       10.10.10.0 (node2)

Cluster manager node: 10.10.10.1 (node1)

It seems that a corruption occured on a particular GPFS config file, named nsdpvol:

 #ls -l /var/mmfs/gen/nsdpvol
-rw-r--r--    1 root     system          0    Feb 24 11:00 /var/mmfs/gen/nsdpvol

See? it is empty. You can check on the other node if it is empty too, this was not the case for me :

 # ls -l /var/mmfs/gen/nsdpvol
-rw-r--r--    1 root     system          127 Feb 24 11:00 /var/mmfs/gen/nsdpvol
# cat /var/mmfs/gen/nsdpvol
hdisk3 gVNX0521_4203_001
hdisk8 gVNX0521_4303_100
hdisk9 gVNX0521_4403_100
hdisk10 gVNX0521_4503_100
hdisk11 gVNX0521_4603_100

So now how do we recover from this ? there is a very simple trick, found on this forum, which basically regenerates this file with the command mmlspv after removing the nsdpvol file :

 # mmlspv
#rm /var/mmfs/gen/nsdpvol
# mmlspv
#hdisk3 gVNX0521_4203_001
hdisk8 gVNX0521_4303_100
hdisk9 gVNX0521_4403_100
hdisk10 gVNX0521_4503_100
hdisk11 gVNX0521_4603_100
# ls -l /var/mmfs/gen/nsdpvol
-rw-r--r--    1 root     system          127 Feb 24 11:00 /var/mmfs/gen/nsdpvol
# cat /var/mmfs/gen/nsdpvol
hdisk3 gVNX0521_4203_001
hdisk8 gVNX0521_4303_100
hdisk9 gVNX0521_4403_100
hdisk10 gVNX0521_4503_100
hdisk11 gVNX0521_4603_100

That’s all !

 #lspv
hdisk4          00f6af60810a2534                    rootvg          active
hdisk5          00f6af608efb31ce                    appsvg          active
hdisk0          none                                None
hdisk1          none                                None
hdisk3          none                                gVNX0521_4203_001
hdisk2          none                                None
hdisk6          none                                None
hdisk7          none                                None
hdisk8          none                                gVNX0521_4303_100
hdisk9          none                                gVNX0521_4403_100
hdisk10         none                                gVNX0521_4503_100
hdisk11         none                                gVNX0521_4603_100

 

 

Links

https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014231266

 

Share Button
GPFS : all my NSDs appear as « none None » in lspv output!

Laisser un commentaire