Creating a new gfs2 filesystem generates "Invalid lock table: invalid character" for an existing Cluster name already containing invalid characters

Solution Verified - Updated -

Issue

  • Unable to create a gfs2 filesystem using the mkfs.gfs2 command containing invalid characters in the LockTableName for an existing Cluster name that has invalid characters
$ mkfs.gfs2 -p lock_dlm -t my.cluster.com:MYdata -j 12 /dev/myVG/MYnewLV
Invalid lock table: invalid character '.'

Environment

  • Red Hat Enterprise Linux 7
  • Pacemaker
  • GFS2

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