The VG minor number in the prod server and the QA server are
inconsistent – this would result in NFS
stale handle errors for the NFS clients after a package
failover
FFile system /sapmnt/DC1 exported to linux server, when package
failover to SYSTEMP12.
Eexport file system on the linux show NFS stale handle.
Iissue:
MMinor number for volume group, /dev/vg_DC1_bin is different on
both the node.
RRecommendations:
NNeed to adapt same minor number on both nodes.
F
fFor DC1 minor number is not same, Resulting in NFS stale handle for exported FS.
fFor DC1 minor number is not same, Resulting in NFS stale handle for exported FS.
[root@SYSTEMS12:/etc/cmcluster/DC1]#
#-> ll /dev/vg_DC1_bin/group
crw-r--r-- 1 root sys
64 0x100000 May 28 2009 /dev/vg_DC1_bin/group
[root@SYSTEMS12:/etc/cmcluster/DC1]#
#-> ssh SYSTEMP12 ll /dev/vg_DC1_bin/group
crw-r----- 1 root sys
64 0x0d0000 Aug 6 20:17 /dev/vg_DC1_bin/group
For AB1 is this OK , so issue of NFS stale handle is not
happen.
[root@SYSTEMS12:/etc/cmcluster/DC1]#
#-> ssh SYSTEMP12 ll /dev/vg_AB1_bin/group
crw-r--r-- 1 root sys
64 0x020000 May 22 2009 /dev/vg_AB1_bin/group
[root@SYSTEMS12:/etc/cmcluster/DC1]#
#-> ll /dev/vg_AB1_bin/group
crw-r--r-- 1 root sys
64 0x020000 Dec 11 2011 /dev/vg_AB1_bin/group
[root@SYSTEMS12:/etc/cmcluster/DC1]#
No comments:
Post a Comment