mkfs.gfs2 command fails with "Invalid character" error in a High Availability cluster

Solution In Progress - Updated -


  • mkfs.gfs2 doesn't allow me to use a locktable name that matches the cluster name in /etc/corosync/corosync.conf.
  • Running mkfs.gfs2 fails with the following type of error:
[root@fastvm-rhel-8-0-23 ~]# mkfs.gfs2 -j2 -p lock_dlm -t rhel8.test:gfs2-demo1 /dev/shared_vg1/shared_lv1
Invalid lock table: invalid character '.'


  • Red Hat Enterprise Linux 7 or 8 (with the 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