LVM command output is inconsistent with metadata on PV after lvextend failed with "Error locking on node"

Solution Unverified - Updated -

Issue

  • LVM command output is inconsistent with metadata on PV after lvextend failed with "Error locking on node"
  • Metadata on physical volume shows that logical volume has been extended, but lvs does not.
# lvextend -l +100%free /dev/vgcluster/app
  Size of logical volume vgcluster/app changed from 200.00 GiB (51200 extents) to <400.00 GiB (102399 extents).
  Error locking on node 2: Aborting.  LV vgcluster/app is now incomplete and '--activationmode partial' was not specified.
  Failed to lock logical volume vgcluster/app.

Environment

  • Red Hat Enterprise Linux Server 7 (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