After building our GFS2 cluster using product documentation, we find our GFS2 filesystem resources failing with "Filesystem(GFS2fs)[123]: WARNING: Couldn't find device [/dev/GFS2vg/GFS2lv]. Expected /dev/??? to exist"

Solution Verified - Updated -

Issue

 Clone Set: dlm-clone [dlm]
     Started: [ node1 node2 ]
 Clone Set: clvmd-clone [clvmd]
     Started: [ node1 node2 ]
 Clone Set: GFS2fs-clone [GFS2fs]
     Stopped: [ node1 node2 ]


Resources:
 Clone: dlm-clone
  Meta Attrs: interleave=true ordered=true
  Resource: dlm (class=ocf provider=pacemaker type=controld)
   Operations: monitor interval=30s on-fail=fence (dlm-monitor-interval-30s)
               start interval=0s timeout=90 (dlm-start-interval-0s)
               stop interval=0s timeout=100 (dlm-stop-interval-0s)
 Clone: clvmd-clone
  Meta Attrs: interleave=true ordered=true
  Resource: clvmd (class=ocf provider=heartbeat type=clvm)
   Attributes: with_cmirrord=true
   Operations: monitor interval=30s on-fail=fence (clvmd-monitor-interval-30s)
               start interval=0s timeout=90 (clvmd-start-interval-0s)
               stop interval=0s timeout=90 (clvmd-stop-interval-0s)
 Clone: GFS2fs-clone
  Meta Attrs: interleave=true
  Resource:  (class=ocf provider=heartbeat type=Filesystem)
   Attributes: device=/dev/GFS2vg/GFS2lv directory=/gfs2 fstype=gfs2 options=noatime
   Operations: monitor interval=10s on-fail=fence (GFS2fs-monitor-interval-10s)
               start interval=0s timeout=60 (GFS2fs-start-interval-0s)
               stop interval=0s timeout=60 (GFS2fs-stop-interval-0s)

  • The pcs status command shows the following errors regarding the GFS2 filesystems:
Failed Actions:
* GFS2fs_start_0 on node1 'not installed' (5): call=26, status=complete, exitreason='Couldn't find device [/dev/GFS2vg/GFS2lv]. Expected /dev/??? to exist',
    last-rc-change='Tue Oct 12 12:46:47 2017', queued=0ms, exec=65ms
* GFS2fs_start_0 on node2 'not installed' (5): call=26, status=complete, exitreason='Couldn't find device [/dev/GFS2vg/GFS2lv]. Expected /dev/??? to exist',
    last-rc-change='Tue Oct 12 12:46:46 2017', queued=0ms, exec=63ms
  • Constraints in this cluster are:
Ordering Constraints:
  start dlm-clone then start clvmd-clone (kind:Mandatory)
Colocation Constraints:
  clvmd-clone with dlm-clone (score:INFINITY)
Ticket Constraints:
  • When the cluster is started, we see that the GFS2 resource is attempted to start before DLM and/or CLVM resource is started, resulting in this error: "Filesystem(GFS2fs)[123]: WARNING: Couldn't find device [/dev/GFS2vg/GFS2lv]. Expected /dev/??? to exist"
Oct 12 12:46:47 node1 Filesystem(GFS2fs)[123]: WARNING: Couldn't find device [/dev/GFS2vg/GFS2lv]. Expected /dev/??? to exist
Oct 12 12:46:48 node1 crmd[121]:  notice: Result of start operation for dlm on node1: 0 (ok)

Environment

Red Hat Enterprise Linux 7 with High Availability Add-On
Red Hat Enterprise Linux 7 with Resilient Storage Add-On

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
Close

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