Unable to start filesystem resource in pacemaker cluster

Solution Verified - Updated -

Issue

  • pcs status shows the following failed action :
Failed Actions:
* fs_start_0 on node3 'unknown error' (1): call=22, status=complete, exitreason='Couldn't mount filesystem /dev/mapper/clusvg-cluslv on /data',
    last-rc-change='Thu Jan 26 23:15:13 2017', queued=0ms, exec=53ms
* fs_start_0 on node1.example.com 'unknown error' (1): call=28, status=complete, exitreason='Couldn't mount filesystem /dev/mapper/clusvg-cluslv on /data',
    last-rc-change='Thu Jan 26 23:15:10 2017', queued=0ms, exec=61ms
* fs_start_0 on node2.example.com 'unknown error' (1): call=22, status=complete, exitreason='Couldn't mount filesystem /dev/mapper/clusvg-cluslv on /data',
    last-rc-change='Thu Jan 26 23:15:11 2017', queued=0ms, exec=97ms

Environment

  • Red Hat Enterprise Linux (RHEL) 6 With High Availability
  • Red Hat Enterprise Linux (RHEL) 7 With High Availability
  • Red Hat Enterprise Linux (RHEL) 8 With High Availability
  • Red Hat Enterprise Linux (RHEL) 9 With High Availability
  • Pacemaker

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