Services using HA-LVM with no "lv_name" attribute are not recovered after a disk failure in RHEL 5 or 6

Solution Verified - Updated -

Issue

  • Services using HA-LVM are not relocated after disk access failure.
  • We've found that, if a node loses access to the storage, lvm resource can not deactivate the VG for the services running in the node:
  • When I simulate a disk failure scenario, lvm resource recovery does not always work as expected.
  • After all physical volumes in a volume group managed by an lvm resource fail, the other node cannot recover it:
Oct  1 18:07:17 node2 rgmanager[10988]: [lvm] Starting volume group, myvg
Oct  1 18:07:17 node2 rgmanager[11027]: [lvm] Someone else owns this volume group

Environment

  • Red Hat Enterprise Linux (RHEL) 5 or 6 with the High Availability Add On
  • HA-LVM (either clvmd or tagging based)
    • Using a "by-vg" configuration: One or more lvm resources in /etc/cluster/cluster.conf that do not have an lv_name attribute specified
  • RHEL 6: resource-agents prior to release 3.9.2-12.el6_3.2 or release 3.9.2-21.el6
  • RHEL 5: rgmanager prior to release 2.0.52-37.el5_9.4 or release rgmanager-2.0.52-47.el5

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

New to Red Hat?

Learn more about Red Hat subscriptions

Close

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