Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Today, mkfs.gfs2 enforces a limit of 16 bytes for cluster name
(and 16 bytes for file system name) in the superblock, even
though there's room for 64 bytes (total) for sb_locktable.
The trouble is, pacemaker / corosync allow much longer cluster
names (not really limited). The dlm_controld seems to have a
64-byte limit*. Customers have complained that they create a
cluster, get it all running, then when they try to make the GFS2
file systems, mkfs.gfs2 rejects the cluster name for being too
long. However, renaming the cluster is not very easy to do.
I'd like to see us double the limit from 16:16 to 32:31 (need
to leave room for the colon).

Version-Release number of selected component (if applicable):
RHEL7.X

How reproducible:
Always

Steps to Reproduce:
# mkfs.gfs2 -O -p lock_dlm -j4 -t "financial_cluster:intec34p" /dev/mpathc/intec34p

Actual results:
locktable error: cluster name too long

Expected results:
No error

Additional info:
*
libdlm/libdlm.h:#define DLM_LOCKSPACE_LEN       64

Created attachment 1018051 [details]
Patch posted upsream

This patch increases the allowed cluster name to 32 bytes along
with increasing the allowed the file system name to 30 bytes.

Verified in gfs2-utils-3.1.8-4:

[root@host-050 ~]# rpm -q gfs2-utils
gfs2-utils-3.1.8-4.el7.x86_64
[root@host-050 ~]# mkfs.gfs2 -O -p lock_dlm -j4 -t "financial_cluster:intec34p" /dev/sda1
This will destroy any data on /dev/sda1
Device:                    /dev/sda1
Block size:                4096
Device size:               200.00 GB (52428544 blocks)
Filesystem size:           200.00 GB (52428541 blocks)
Journals:                  4
Resource groups:           802
Locking protocol:          "lock_dlm"
Lock table:                "financial_cluster:intec34p"
UUID:                      be01bc30-ede8-762b-a06d-50a1e180e9b6

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2178.html