Why does the start operation of GFS2 Filesystem resource fails with the message "dlm_new_lockspace error -53"?

Solution Verified - Updated -

Issue

  • After creating the Filesystem resource for managing a GFS2 file system, Pacemaker cannot start the resource and it fails with the following message:

    kernel: dlm: dlm cluster name 'testcluster' does not match the application cluster name 'my_cluster'
kernel: gfs2: fsid=my_cluster:gfs2-demo: dlm_new_lockspace error -53

Environment

Red Hat Enterprise Linux 8 with Resilient Storage Add-On
GFS2 File system

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