Saturday, October 19, 2013

How to Unlock the VXFS file system when it is configured in VCS

DHEEMTANANA.COM

How to Unlock the VXFS file system when it is configured in VCS

This attribute is only applicable to Veritas (VxFS) file systems. This attribute controls a file system locking feature to prevent accidental unmounts.  
This attribute can take three values: 0, 1, or 2. 
VxFSMountLock=0 
The resource does not detect any changes to the lock when VCS reports that it is online after you set the value to zero. 
·          If the mount point is initially locked with the mntlock="VCS", the monitor agent function unlocks it.
·          If the mount point is initially locked with a key that is not equal to "VCS", a message is logged once or the agent logs a message once.
·          If the mount point is initially not locked, no action is performed.
VxFSMountLock=1 
The resource does not detect changes to the lock when VCS reports it online after the value was set to one. VCS does not monitor the lock. 
·          If the mount point is initially locked with the mntlock="VCS", no action is performed.
·          If the mount point is initially locked with a key that is not equal to "VCS", a message is logged once or the agent logs a message once.
·          If the mount point is initially not locked, the monitor agent function locks it with the mntlock="VCS".
VxFSMountLock=2 
When the value of the VxFSMountLock is 2, the file system is locked and the agent monitors any change to mntlock. 
·          If the mount point is locked with the mntlock="VCS", no action is performed.
·          If the mount point is initially locked with a key that is not equal to "VCS", the monitor agent function logs a message whenever a change in mntlock is detected.
·          If the mount point is not locked, the agent locks it with the mntlock="VCS".
Type and dimension: integer-scalar 
Default: 1 


Issue
UX:vxfs umount: ERROR: V-3-26360: file system /zoneroot/ufsvol/z-a has been mount locked

Solution


ISSUE: 5.0 MP3 Mount Agent cannot umount  a nested vxfs filesystem when the VxFSMountLock attribute is set to 1.

SYMPTOMS: After a forced umount of the ufs-mount in /zoneroot/ufs-mount/vxfs-mount, the following error is encountered:

2009/03/10 15:14:15 VCS INFO V-16-10001-5560 (sprst1000a0-14) Mount:gateway-z-a:
clean:The filesystem mounted on /zoneroot/ufsvol/z-a is locked by key VCS. Unlocking it.
/zoneroot/ufsvol/z-a: fuser: No such file or directory
UX:vxfs umount: ERROR: V-3-26360: file system /zoneroot/ufsvol/z-a has been mount locked
/zoneroot/ufsvol/z-a: fuser: No such file or directory

DETAILS:
Here is an excerpt of the engine_A.log when VxFSMountLock is set to 1:
----------------------------------------------------------
2009/03/10 15:14:07 VCS ERROR V-16-2-13077 (sprst1000a0-14) Agent is unable to offline resource(gateway-z-a). Administrative intervention may be required.
....truncated...followed by unsuccessful fuser attempts
2009/03/10 15:14:15 VCS INFO V-16-10001-5560 (sprst1000a0-14) Mount:gateway-z-a:clean:The filesystem mounted on /zoneroot/ufsvol/z-a is locked by key VCS. Unlocking it.
/zoneroot/ufsvol/z-a: fuser: No such file or directory
UX:vxfs umount: ERROR: V-3-26360: file system /zoneroot/ufsvol/z-a has been mount locked
/zoneroot/ufsvol/z-a: fuser: No such file or directory
----------------------------------------------------------

Here is an excerpt of the engine_A.log when VxFSMountLock is set to 0:
----------------------------------------------------------
2009/03/10 15:37:25 VCS ERROR V-16-2-13067 (sprst1000a0-13) Agent is calling clean for resource(gateway-ufs) because the resource became OFFLINE unexpectedly, on its own.
2009/03/10 15:37:26 VCS INFO V-16-2-13068 (sprst1000a0-13) Resource(gateway-ufs) - clean completed successfully.
2009/03/10 15:37:26 VCS INFO V-16-1-10307 Resource gateway-ufs (Owner: unknown,
Group: lame) is offline on sprst1000a0-13 (Not initiated by VCS)
2009/03/10 15:37:26 VCS NOTICE V-16-1-10300 Initiating Offline of Resource zone
(Owner: unknown, Group: lame) on System sprst1000a0-13
2009/03/10 15:37:26 VCS NOTICE V-16-1-10300 Initiating Offline of Resource gateway-z-a (Owner: unknown, Group: lame) on System sprst1000a0-13
2009/03/10 15:37:27 VCS INFO V-16-6-15004 (sprst1000a0-13) hatrigger:Failed to send trigger for resfault; script doesn't exist
2009/03/10 15:37:33 VCS INFO V-16-2-13001 (sprst1000a0-13) Resource(gateway-z-a): Output of the completed operation (offline)
UX:vxfs fsadm: ERROR: V-3-20275: cannot open /zoneroot/ufsvol/z-a
df: cannot statvfs /zoneroot/ufsvol/z-a: No such file or directory
2009/03/10 15:37:33 VCS INFO V-16-1-10305 Resource gateway-z-a (Owner: unknown,
Group: lame) is offline on sprst1000a0-13 (VCS initiated) <--------VCS offlines VxFSMountLock=0 fs as expected
----------------------------------------------------------
WORKAROUND: This issue does not occur when the VxFSMountLock attribute of the mount resource is set to 0 (zero). Here are the commands to do so.
#haconf -makerw
#hares -modify <resource> VxFSMountLock 0
#haconf -dump -makr0


0 comments:

Post a Comment

 
Design by BABU | Dedicated to grandfather | welcome to BABU-UNIX-FORUM