Cluster service with an lvm resource fails to relocate with error 'Someone else owns this logical volume' when using lvm2-lvmetad in a RHEL 6 High Availability cluster

Solution Verified - Updated -

Issue

  • The cluster service is failing to relocate from one node to another and shows following error messages:

    Jul  1 11:31:06 node1 rgmanager[3674]: Starting stopped service service:testservice
    Jul  1 11:31:06 node1 rgmanager[4996]: [lvm] Someone else owns this logical volume          <---
    Jul  1 11:31:06 node1 rgmanager[3674]: start on lvm "halvm1" returned 1 (generic error)
    Jul  1 11:31:07 node1 rgmanager[3674]: #68: Failed to start service:testservice; return value: 1
    Jul  1 11:31:07 node1 rgmanager[3674]: Stopping service service:testservice
    [...]
    

    Cluster service fails to start only on one node, other node is able to start this service without any issues.

Environment

  • Red Hat Enterprise Linux (RHEL) 6 with the High Availability Add On
  • rgmanager
  • HA-LVM with the tagging variant
    • locking_type = 1 in /etc/lvm/lvm.conf
    • One or more <lvm> resources in /etc/cluster/cluster.conf
  • lvm2-lvmetad service running on some, but not all, cluster nodes

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