clvmd init script fails to start or stop with exclusively activated volumes in the cluster in RHEL 5.6

Solution Verified - Updated -

Issue

  • On system bootup, the clvmd service fails on activating the volumes when using HA-LVM with clvmd, and a volume is activated exclusively on another node
  • The clvmd init script fails when starting if a volume is activated exclusively on another node

    Starting clvmd: 
    Activating VG(s):   Error locking on node node2: Volume is busy on another node
      0 logical volume(s) in volume group "myvg" now active
                                                               [FAILED]
    
  • When clvmd fails to start on bootup because a volume is busy on another node, the clvmd service will not stop on shutdown, causing the cman service stop to fail, and the system will not shutdown

  • Access a node's storage page in the Conga web interface results in the error "Host responded - clvmd failed to start"

Environment

  • Red Hat Enterprise Linux (RHEL) 5 Update 4 through Update 6

  • Red Hat Enterprise Linux 5 Advanced Platform (Clustering)

  • lvm2-cluster prior to version 2.02.84-6.el5
  • HA-LVM using the clvmd variant https://access.redhat.com/kb/docs/DOC-3068 or usage of exclusively activated volumes within the cluster

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