clusterfs resource fails to start with "startFilesystem: Could not match /dev/vg/lv with a real device" in RHEL 5 or 6 cluster

Solution Unverified - Updated -

Issue

  • Service fails to start a clusterfs resource
Jun 14 21:17:38 zmy12ln02 clurgmgrd[6026]: <notice> Starting stopped service service:myService
Jun 14 21:17:38 zmy12ln02 clurgmgrd: [6026]: <err> startFilesystem: Could not match /dev/vg01/lv01 with a real device 
Jun 14 21:17:41 zmy12ln02 clurgmgrd: [6026]: <err> startFilesystem: Could not match /dev/vg01/lv01 with a real device 
Jun 14 21:17:44 zmy12ln02 clurgmgrd: [6026]: <err> startFilesystem: Could not match /dev/vg01/lv01 with a real device 
Jun 14 21:17:47 zmy12ln02 clurgmgrd[6026]: <notice> start on clusterfs "gfs1" returned 2 (invalid argument(s))
  • Primary node was down but clusterfs were not moved to secondary node and the status was failed.

Environment

  • Red Hat Enterprise Linux (RHEL) 5 with the Resilient Storage Add On
  • Red Hat Enterprise Linux (RHEL) 6 with the Resilient Storage Add On
  • Cluster service containing <clusterfs> resource(s)
  • GFS/GFS2
  • lvm2-cluster
    • locking_type = 3 in /etc/lvm/lvm.conf

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