Cluster service fails while starting or stopping with 'start_filesystem: Could not match <device> with a real device' in RHEL 6

Solution Verified - Updated -

Issue

  • When stopping a service after it has already been stopped, it fails on 'Could not match with a real device' and goes to a failed state
  • When my service fails to start, it then attempts to stop before recovery. If the lvm resource never got started in the first place, this stop attempt will fail, leaving the service in a failed state rather than recovering on another node:
Nov 19 11:39:15 node1 rgmanager[6412]: Stopping service service:myservice
Nov 19 11:39:16 node1 rgmanager[8394]: [fs] stop: Could not match /dev/vg01/lv01 with a real device
Nov 19 11:39:16 node1 rgmanager[6412]: stop on fs "lv01" returned 2 (invalid argument(s))
Nov 19 11:39:16 node1 rgmanager[6412]: #12: RG service:myservice failed to stop; intervention required
Nov 19 11:39:16 node1 rgmanager[6412]: Service service:myservice is failed
  • Any attempt to stop a service where the fs resource's device was not activated results in the service failing

Environment

  • Red Hat Enterprise Linux (RHEL) 6 with the High Availability Add On
  • A cluster service in /etc/cluster/cluster.conf containing an fs, clusterfs, or netfs resource
    • The fs resource must require activation as part of the service, such as with an lvm resource
  • Failure occurs during start or stop of an fs, clusterfs, or netfs resource
    • There is a similar solution for this error occurring during status checks of these resources

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