Cluster managed filesystem resource fails to start with error "Couldn't mount device [/dev/clustervg/clusterlv1] as /mountpoint".

Solution Verified - Updated -

Issue

  • Filesystem resource is failing to start with the below errors
Mar  1 01:00:51 rhel7-node1 Filesystem(fileys2)[7773]: INFO: Running start for /dev/clustervg/clusterlv1 on /mountpoint
Mar  1 01:00:52 rhel7-node1 Filesystem(fileys2)[7773]: ERROR: Couldn't mount device [/dev/clustervg/clusterlv1] as /mountpoint
Mar  1 01:00:52 rhel7-node1 lrmd[1219]:  notice: fileys2_start_0:7773:stderr [  ]
Mar  1 01:00:52 rhel7-node1 lrmd[1219]:  notice: fileys2_start_0:7773:stderr [ Usage: ]
Mar  1 01:00:52 rhel7-node1 lrmd[1219]:  notice: fileys2_start_0:7773:stderr [  mount [-lhV] ]
Mar  1 01:00:52 rhel7-node1 lrmd[1219]:  notice: fileys2_start_0:7773:stderr [  mount -a [options] ]
Mar  1 01:00:52 rhel7-node1 lrmd[1219]:  notice: fileys2_start_0:7773:stderr [  mount [options] [--source] <source> | [--target] <directory> ]
Mar  1 01:00:52 rhel7-node1 lrmd[1219]:  notice: fileys2_start_0:7773:stderr [  mount [options] <source> <directory> ]
Mar  1 01:00:52 rhel7-node1 lrmd[1219]:  notice: fileys2_start_0:7773:stderr [  mount <operation> <mountpoint> [<target>] ]
Mar  1 01:00:52 rhel7-node1 lrmd[1219]:  notice: fileys2_start_0:7773:stderr [  ]
  • Couldn't get the filesystem resource in the cluster started state.

Environment

Red Hat Enterprise Linux 7, 8 with High Availability Add-on
Red Hat Enterprise Linux 7, 8 with 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