Why GFS2 filesystem is not starting automatically after reboot?

Solution Verified - Updated -


  • GFS2 filesystem is stopped after system is fenced
  • GFS2 filesystem is stopped after system is rebooted
  • Cluster GFS2 resource is not starting after cluster services starts
  • The resource gfs2-clone didn't start on node2 after the node rejoins the cluster. Snippet of pcs output below:

    Online: [ node1 node2 ]
    Full list of resources:
    Clone Set: dlm-clone [dlm]
        Started: [ node1 node2 ]
    Clone Set: clvmd-clone [clvmd]
        Started: [ node1 node2 ]
    Clone Set: gfs2-clone [gfs2]
        Started: [ node1 ]
        Stopped: [ node2 ]
    Failed Actions:
    * gfs2_start_0 on node2 'not installed' (5): call=27, status=complete, exitreason='Couldn't find device [/dev/cluster_vg/cluster_lv]. Expected /dev/??? to exist',  last-rc-change='Fri Apr  5 11:21:24 2019', queued=0ms, exec=74ms


  • Red Hat Enterprise Linux (RHEL) 7 with the High Availability Or Resilient Storage Add On

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