Restarting the vxconfigd daemon on the slave node after a disk is removed from all nodes may cause the disk groups to be disabled on the slave node (3591019)
The issue occurs if the storage connectivity of a disk is removed from all the nodes of the cluster and the
vxconfigd daemon is restarted on the slave node before the disk is detached from the slave. All the disk groups are in the dgdisabled state on the slave node, but show as enabled on the other nodes.
If the disk was detached before the
vxconfigd daemon is restarted, the issue does not occur.
In a Flexible Storage Sharing (FSS) environment, removing the storage connectivity on a node that contributes DAS storage to a shared disk group results in global connectivity loss because the storage is not connected elsewhere.
Related information
Workaround:
To prevent this issue:
Before restarting the
vxconfigd daemon, if a disk in a shared disk group has lost connectivity to all nodes in the cluster, make sure that the disk is in the detached state. If a disk needs to be detached, use the following command:
\# vxdisk check diskname
To resolve the issue after it has occurred:
If
vxconfigd is restarted before the disks got detached, remove the node from the cluster and rejoin the node to the cluster.