- If I freeze my services and reboot all nodes, lvm resources fail to start back up with "nodeX owns VG and is still a cluster member"
- During a scheduled maintenance two node cluster was rebooted, but the cluster services failed to start automatically and following error messages were observed:
Dec 19 02:57:19 node1 rgmanager: [lvm] node2 owns myVG and is still a cluster member Dec 19 02:57:25 node1 rgmanager: Services Initialized Dec 19 02:57:26 node1 rgmanager: [lvm] Starting volume group, myVG Dec 19 02:57:26 node1 rgmanager: [lvm] node2 owns myVG and is still a cluster member Dec 19 02:57:26 node1 rgmanager: [lvm] Someone else owns this volume group Dec 19 02:57:26 node1 rgmanager: start on lvm "myVG" returned 1 (generic error) Dec 19 02:57:26 node1 rgmanager: #68: Failed to start service:myService; return value: 1
- Red Hat Enterprise Linux (RHEL) 6 with the High Availability Add On
- HA-LVM with tagging
lv_nameblank or unspecified in
- Services frozen with
clusvcadm -Zbefore reboot or shutdown of rgmanager, or nodes were shut down "uncleanly" without properly stopping service containing
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.