cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Paul Evans <pevans@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] mkfs.gfs2: Allow longer cluster names
Date: Tue, 21 Apr 2015 16:52:47 +0100	[thread overview]
Message-ID: <1429631567-18662-1-git-send-email-pevans@redhat.com> (raw)

Increase the enforced limit for cluster name to 32 bytes and file
system name to 30 bytes for mkfs.gfs2 (was previously 16 + 16
bytes).

Also increased this limit in tunegfs2 when relabling gfs2 file
sytems.

Updated the formation in the man pages along with adding a new test
case for mkfs.gfs2 to validate the increased cluster/file system
name support.
---
 gfs2/man/mkfs.gfs2.8  | 2 +-
 gfs2/mkfs/main_mkfs.c | 4 ++--
 gfs2/tune/super.c     | 2 +-
 tests/mkfs.at         | 6 ++++++
 4 files changed, 10 insertions(+), 4 deletions(-)

diff --git a/gfs2/man/mkfs.gfs2.8 b/gfs2/man/mkfs.gfs2.8
index ceb6f38..44483f1 100644
--- a/gfs2/man/mkfs.gfs2.8
+++ b/gfs2/man/mkfs.gfs2.8
@@ -103,7 +103,7 @@ It is \fIclustername:fsname\fR.
 Clustername must match that in cluster.conf; only members of this
 cluster are permitted to use this file system.
 Fsname is a unique file system name used to distinguish this GFS2 file
-system from others created (1 to 16 characters).  Lock_nolock doesn't
+system from others created (1 to 30 characters).  Lock_nolock doesn't
 use this field. Valid \fIclustername\fRs and \fIfsname\fRs may only contain
 alphanumeric characters, hyphens (-) and underscores (_).
 .TP
diff --git a/gfs2/mkfs/main_mkfs.c b/gfs2/mkfs/main_mkfs.c
index 0636f0b..3fab08c 100644
--- a/gfs2/mkfs/main_mkfs.c
+++ b/gfs2/mkfs/main_mkfs.c
@@ -398,7 +398,7 @@ static void test_locking(const char *lockproto, const char *locktable)
 
 		if (c == locktable)
 			die("%s %s\n", errprefix, _("cluster name is missing"));
-		if (c - locktable > 16)
+		if (c - locktable > 32)
 			die("%s %s\n", errprefix, _("cluster name is too long"));
 
 		c++;
@@ -406,7 +406,7 @@ static void test_locking(const char *lockproto, const char *locktable)
 			die("%s %s\n", errprefix, _("contains more than one colon"));
 		if (!strlen(c))
 			die("%s %s\n", errprefix, _("file system name is missing"));
-		if (strlen(c) > 16)
+		if (strlen(c) > 30)
 			die("%s %s\n", errprefix, _("file system name is too long"));
 	} else {
 		die( _("Invalid lock protocol: %s\n"), lockproto);
diff --git a/gfs2/tune/super.c b/gfs2/tune/super.c
index cbd0026..560ce68 100644
--- a/gfs2/tune/super.c
+++ b/gfs2/tune/super.c
@@ -194,7 +194,7 @@ int change_locktable(struct tunegfs2 *tfs, const char *locktable)
 			fprintf(stderr, "%s %s\n", errpre, _("missing colon"));
 			return EX_DATAERR;
 		}
-		if (strlen(++fsname) > 16) {
+		if (strlen(++fsname) > 30) {
 			fprintf(stderr, "%s %s\n", errpre, _("file system name is too long"));
 			return EX_DATAERR;
 		}
diff --git a/tests/mkfs.at b/tests/mkfs.at
index 438184c..786f30c 100644
--- a/tests/mkfs.at
+++ b/tests/mkfs.at
@@ -89,3 +89,9 @@ AT_SETUP([Min. quota change file size])
 AT_KEYWORDS(mkfs.gfs2 mkfs)
 GFS_FSCK_CHECK([$GFS_MKFS -p lock_nolock -c 1 $GFS_TGT])
 AT_CLEANUP
+
+AT_SETUP([Incr. cluster/file system name support])
+AT_KEYWORDS(mkfs.gfs2 mkfs)
+GFS_FSCK_CHECK([$GFS_MKFS -p lock_dlm -t "financial_cluster:intec34p" $GFS_TGT])
+GFS_FSCK_CHECK([$GFS_MKFS -p lock_dlm -t "financial_cluster:financial_volume-001" $GFS_TGT])
+AT_CLEANUP
-- 
1.9.3



             reply	other threads:[~2015-04-21 15:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-21 15:52 Paul Evans [this message]
2015-04-21 17:01 ` [Cluster-devel] [PATCH] mkfs.gfs2: Allow longer cluster names Andrew Price
  -- strict thread matches above, loose matches on Subject: below --
2015-04-22 16:44 Paul Evans
2015-04-22 18:01 ` Andrew Price
2015-04-22 18:09 ` Bob Peterson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1429631567-18662-1-git-send-email-pevans@redhat.com \
    --to=pevans@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).