LVM-activate resource using lvmlockd fails to start after changing the cluster name.

Solution Unverified - Updated -

Issue

  • I want to change the cluster name that has associated GFS2 filesystem(s).
  • The LVM-activate resource fails to start after changing the cluster name.
  • How to change the dlm cluster name in the VG when the dlm cluster name is already changed on the hosts.

  • LVM-activate resource fails to start with the below errors.

May 10 11:38:10 rhel8-node1 lvmlockd[3453269]: 1620661090 prepare_lockspace_dlm lvm_gfs2_vg mismatching cluster names sys RHEL8-Cluster arg Cluster
May 10 11:38:10 rhel8-node1 LVM-activate(sharedlv1)[3453302]: ERROR:  VG gfs2_vg start failed: invalid parameters for dlm
May 10 11:38:10 rhel8-node1 LVM-activate(sharedlv1)[3453302]: ERROR: Failed to start shared VG(s), exit code: 5
May 10 11:38:10 rhel8-node1 LVM-activate(sharedlv1)[3453302]: ERROR: gfs2_vg/gfs2_lv: failed to activate.
May 10 11:38:10 rhel8-node1 pacemaker-execd[3453025]: notice: sharedlv1_start_0:3453302:stderr [   Reading VG gfs2_vg without a lock. ]
May 10 11:38:10 rhel8-node1 pacemaker-execd[3453025]: notice: sharedlv1_start_0:3453302:stderr [ ocf-exit-reason:gfs2_vg/gfs2_lv: failed to activate. ]
May 10 11:38:10 rhel8-node1 pacemaker-controld[3453028]: notice: Result of start operation for sharedlv1 on clu-node1: 1 (error)

Environment

Red Hat Enterprise Linux 8 with Resilient Storage add-ons.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content