Failure to (re)import a single shared diskgroup during Cluster Volume Manager master takeover results in all shared diskgroups being disabled and node eviction from cluster
|Article:TECH193261|||||Created: 2012-07-18|||||Updated: 2012-10-13|||||Article URL http://www.symantec.com/docs/TECH193261|
During Cluster Volume Manager (CVM) master takeover, all shared diskgroups undergo a re-import. Volume Manager (VxVM) disables all shared diskgroups (dgdisable) when a single shared diskgroup fails to import. It also results in the corresponding node (new master) leaving the cluster.
Aug 11 22:38:35 hostname vxvm:vxconfigd: [ID 702911 daemon.error] V-5-1-7934 Disk group dgname1: Disabled by errors
Aug 11 22:38:35 hostname vxvm:vxconfigd: [ID 702911 daemon.error] V-5-1-7934 Disk group dgname2: Disabled by errors
PLATFORMS: ALL : Solaris, HPUX, LINUX & AIX
VxVM versions: 5.0.x ; 5.1.x & 6.0.x
The code path traversed during CVM master takeover exposed a bug that resulted in all shared diskgroups being disabled due to a single shared diskgroup's failure to import.
Code changes were made to disable only the specific shared diskgroup that experienced the failure. Re-import will skip the failed diskgroup and continue importing the rest of shared diskgroups thus preventing node eviction from the cluster.
Patch links for SFHA 5.1SP1RP3
Do not disable other DGs when a re-import of a DG fails during master take-over
Article URL http://www.symantec.com/docs/TECH193261