LVM commands fail with "Global lock failed: check that lvmlockd is running" after deleting an lvmlockd resource in a Pacemaker cluster

Solution Verified - Updated -

Issue

  • I deleted an ocf:heartbeat:lvmlockd resource from a Pacemaker cluster, and now LVM commands like pvcreate and vgcreate fail. The errors say the failure is due to lvmlockd not running.
# pvcreate /dev/xvdl
  WARNING: lvmlockd process is not running.
  Global lock failed: check that lvmlockd is running.
# vgcreate --shared shared_vg_bckp /dev/xvdl
  WARNING: lvmlockd process is not running.
  Failed to detect a running lock manager to select lock type.
  Run `vgcreate --help' for more information.

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.

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