From: rpeterso@sourceware.org <rpeterso@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/gfs2 man/mkfs.gfs2.8 mkfs/main_mkfs.c
Date: 19 Dec 2006 17:52:15 -0000 [thread overview]
Message-ID: <20061219175215.21230.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Branch: RHEL5
Changes by: rpeterso at sourceware.org 2006-12-19 17:52:14
Modified files:
gfs2/man : mkfs.gfs2.8
gfs2/mkfs : main_mkfs.c
Log message:
Resolves: bz 219878: gfs2 creation should default to 1 journal
and lock_nolock
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs2/man/mkfs.gfs2.8.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.1.2.2&r2=1.1.2.3
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs2/mkfs/main_mkfs.c.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.8.2.2&r2=1.8.2.3
--- cluster/gfs2/man/mkfs.gfs2.8 2006/11/30 15:29:48 1.1.2.2
+++ cluster/gfs2/man/mkfs.gfs2.8 2006/12/19 17:52:14 1.1.2.3
@@ -1,5 +1,5 @@
.\" Copyright (C) Sistina Software, Inc. 1997-2003 All rights reserved.
-.\" Copyright (C) 2004 Red Hat, Inc. All rights reserved.
+.\" Copyright (C) 2004-2006 Red Hat, Inc. All rights reserved.
.TH mkfs.gfs2 8
@@ -31,7 +31,8 @@
.TP
\fB-j\fP \fINumber\fR
The number of journals for gfs2_mkfs to create. You need at least one
-journal per machine that will mount the filesystem.
+journal per machine that will mount the filesystem. If this option is
+not specified, one journal will be created.
.TP
\fB-O\fP
This option prevents gfs2_mkfs from asking for confirmation before writing
@@ -41,7 +42,8 @@
LockProtoName is the name of the locking protocol to use. Acceptable
locking protocols are \fIlock_dlm\fR or if you are using GFS2
as a local filesystem (\fB1 node only\fP), you can specify the
-\fIlock_nolock\fR protocol.
+\fIlock_nolock\fR protocol. If this option is not specified,
+\fIlock_nolock\fR protocol will be assumed.
.TP
\fB-q\fP
Be quiet. Don't print anything.
--- cluster/gfs2/mkfs/main_mkfs.c 2006/11/30 15:29:48 1.8.2.2
+++ cluster/gfs2/mkfs/main_mkfs.c 2006/12/19 17:52:14 1.8.2.3
@@ -87,6 +87,8 @@
int optchar;
sdp->device_name = NULL;
+ sdp->md.journals = 1;
+ strcpy(sdp->lockproto, "lock_nolock");
while (cont) {
optchar = getopt(argc, argv, "-c:DhJ:j:Op:qr:t:u:VX");
next reply other threads:[~2006-12-19 17:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 17:52 rpeterso [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-19 17:53 [Cluster-devel] cluster/gfs2 man/mkfs.gfs2.8 mkfs/main_mkfs.c rpeterso
2006-12-19 17:49 rpeterso
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=20061219175215.21230.qmail@sourceware.org \
--to=rpeterso@sourceware.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.