lvmlockd: add_lockspace_dlm shared-vg adopt 0 error

Solution In Progress - Updated -

Issue

  • After creating more than 100+ volume groups, the lock-start command start failing:

    # vgchange --lock-start cluster-vg100
     lvmlockd[<PID>]: <PID> add_lockspace_dlm cluster-vg100 adopt 0 error
    
  • Due to the lock-start failure, the LVM-Activate resource is unable to start:

    # pcs resource debug-start cluster-vg100
    Operation force-start for cluster-vg100 (ocf:heartbeat:LVM-activate) returned 1 (error: cluster-vg100: failed to activate.)
    Reading VG cluster-vg100 without a lock.
    May 20 10:06:39 INFO: Activating cluster-vg100
    May 20 10:06:42 INFO:  VG cluster-vg100 starting dlm lockspace Starting locking. Waiting until locks are ready... 
    May 20 10:06:42 ERROR:  Cannot access VG cluster-vg100 due to failed lock.   ---------> error seen 
    ocf-exit-reason:cluster-vg100: failed to activate.
    

Environment

  • Red Hat Enterprise Linux (RHEL) Server 8 with the Resilient Storage Add On
  • Distributed Lock Manager (dlm)
  • lvm2-lvmlockd

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