The tunegfs2 command fails to change the name of the "Lock table" for a gfs2 filesystem

Environment

• Red Hat Enterprise Linux Server 7 (with the High Availability Add On and Resilient Storage Add Ons)
• A Global Filesystem 2(gfs2)

Issue

• The tunegfs2 command fails to change the name of the "Lock table" for a gfs2 filesystem. The locktable name is not changed.

# tunegfs2 -l /dev/shared_vg/data | grep table
Lock table: rhel7gfs2:gfs2data1lock
# tunegfs2 -l /dev/shared_vg/log | grep table
Lock table: rhel7gfs:gfs2log2lock
# tunegfs2 -o locktable=rhel7cluster:gfs2data1lock /dev/shared_vg/data
# tunegfs2 -l /dev/shared_vg/data | grep table
Lock table: rhel7gfs2:gfs2data1lock

Resolution

Try changing the locktable name with the gfs2_edit command.

To list the locktable name:

# gfs2_edit -p sb field sb_locktable /dev/shared_vg/data 

To change locktable name.

# gfs2_edit -p sb field sb_locktable "rhel7cluster:gfs2data1lock" /dev/shared_vg/data 

Root Cause

The lock table name of a gfs2 filesystem can be changed using the command outlined in this solution: Why do I get 'fs is for different cluster' when I attempt to mount a GFS or GFS2 filesystem? or Do I need to make changes to my GFS/GFS2 file systems when renaming the cluster in RHEL?

In some cases the command outlined in those articles does not change the locktable name.

Diagnostic Steps

• Are there any other cluster nodes or clusters that might have the filesystem mounted?
• Are they doing any backups or snapshots and have the filesystem mounted on a non-cluster node?

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.