LVM commands in a cluster reporting "Error locking on node" in RHEL

Solution Verified - Updated -

Issue

  • LVM commands operating on clustered volume groups return errors such as "Error locking on node "
  Error locking on node dcs-unixeng-test3: Aborting.  LV pvmove0 is now incomplete and --partial was not specified.
  • While creating the pv and vg on a cluster node an error is seen:
# lvcreate -n new_lv -l 100 new_vg
Error locking on node node2.localdomain: Volume group for uuid not found: hKRe2KBpgj73fkm5P9ZAppdPsX3Se7EkHL0VzomUkq4gVIrTVeZvTr1ym67Keenh 
Aborting. Failed to activate new LV to wipe the start of it. 
  • I added new shared storage devices in my cluster and am attempting to vgextend, lvextend, or lvcreate and see errors stating "Error locking on node"

Environment

  • Red Hat Cluster Suite (RHCS) 4
  • Red Hat Enterprise Linux (RHEL) 5 with the Resilient Storage Add On
  • Red Hat Enterprise Linux (RHEL) 6 with the Resilient Storage Add On
  • lvm2-cluster (clvmd)
  • One or more volume groups with the clustered ('c') attribute set

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.