GFS2 share not mounting even after Filesystem resource has been created in pacemaker

Solution Verified - Updated -

Issue

  • GFS2 share not mounting even after Filesystem resource has been created in pacemaker.
  • Command pcs status gives the following error even after Filesystem resource has been created for gfs2.

    Failed Actions:
    clusterfs_start_0 on node1 'unknown error' (1): call=37, status=complete, exitreason='Couldn't mount filesystem /dev/vg/lv on /gfs_mountpoint', last-rc-change='Wed Sep 23 13:18:41 2015', queued=0ms, exec=112ms
    clusterfs_start_0 on node2 'unknown error' (1): call=31, status=complete, exitreason='Couldn't mount filesystem /dev/vg/lv on /gfs_mountpoint', last-rc-change='Wed Sep 23 13:18:41 2015', queued=0ms, exec=121ms
    

Environment

  • Red Hat Enterprise Linux (RHEL) 6, or 7 with the Resilient Storage Add On
  • Global Filesystem 2(GFS2)

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