An LVM-activate resource fails to start with error lvmlockd[XXXX]: XXXXXX prepare_lockspace_dlm vg1 mismatching cluster names sys new_clustername arg old_clustername in a Pacemaker cluster
Issue
- An
ocf:heartbeat:LVM-activateresource fails to start after changing the cluster name, and/var/log/messagesshows the following log sequence.
Mar 3 14:10:27 node1 LVM-activate(sharedlv1)[6265]: INFO: Activating vg1/lv1
Mar 3 14:10:27 node1 lvmlockd[1913]: 1646345427 prepare_lockspace_dlm vg1 mismatching cluster names sys old_clustername arg new_clustername
...
Mar 3 14:10:27 node1 LVM-activate(sharedlv1)[6265]: ERROR: VG vg1 start failed: invalid parameters for dlm
Mar 3 14:10:27 node1 LVM-activate(sharedlv1)[6265]: ERROR: Failed to start shared VG(s), exit code: 5
Mar 3 14:10:28 node1 LVM-activate(sharedlv1)[6265]: ERROR: vg1/lv1 failed to activate.
Mar 3 14:10:28 node1 pacemaker-execd[2561]: notice: sharedlv1_start_0[6265] error output [ Reading VG vg1 without a lock. ]
Mar 3 14:10:28 node1 pacemaker-execd[2561]: notice: sharedlv1_start_0[6265] error output [ ocf-exit-reason:vg1/lv1: failed to activate. ]
Mar 3 14:10:28 node1 pacemaker-controld[2564]: notice: Result of start operation for sharedlv1 on node1: error
Environment
- Red Hat Enterprise Linux 8 (with the Resilient Storage Add-on)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
