clvmd: 'Error locking on node XXX: Volume group for uuid not found' after adding new devices in RHEL 4.6 and earlier and 5.4 and earlier

Solution Verified - Updated -

Issue

  • When running lvchange, lvextend or lvremove on a local logical volume in a cluster you can get the following error:

    # lvextend -L +50 G /dev/vg_data/lv_data
    Extending logical volume to 100 GB lv_data
       Error locking on node NodeId: Volume group for uuid not found: <UUID>
       Failed to suspend lv_data
    
  • Having problem creating a LV on a shared LVM VG.

    # lvcreate -L 10g -n lvolxx sqlamsvg0  
     Error locking on node node2: Refusing activation of partial LV lvolxx. Use --partial to override.  
     Aborting. Failed to activate new LV to wipe the start of it.
    
  • After enabling the cluster in lvm, getting following error:

    Error locking on node node1: Command timed out
    Error locking on node node2: Command timed out
    Error locking on node node3: Command timed out
    

Environment

  • Red Hat Cluster Suite (RHCS) 4
  • Red Hat Enterprise Linux (RHEL) 5 Update 4 and earlier with the Resilient Storage Add On
  • lvm2-cluster prior to release 2.02.37-3.el4 in RHEL 4, or prior to release 2.02.56-7.el5 in RHEL 5
  • One ore more volume groups with the clustered ('c') attribute set

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