[Cluster-devel] cluster fence/man/fence.8 gfs/man/gfs_mkfs.8 g ...

rpeterso at sourceware.org rpeterso at sourceware.org
Tue Jan 16 19:11:31 UTC 2007 

CVSROOT:	/cvs/cluster
Module name:	cluster
Branch: 	RHEL5
Changes by:	rpeterso at sourceware.org	2007-01-16 19:11:30

Modified files:
	fence/man      : fence.8 
	gfs/man        : gfs_mkfs.8 gfs_mount.8 
	gfs2/man       : gfs2_mount.8 

Log message:
	Resolves: bz 222747: Remove references to lock_gulm from cluster man pages

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/fence/man/fence.8.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.4&r2=1.4.2.1
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs/man/gfs_mkfs.8.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.3.2.1&r2=1.3.2.2
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs/man/gfs_mount.8.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.5&r2=1.5.2.1
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs2/man/gfs2_mount.8.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.4&r2=1.4.2.1

--- cluster/fence/man/fence.8	2005/02/15 04:47:00	1.4
+++ cluster/fence/man/fence.8	2007/01/16 19:11:30	1.4.2.1
@@ -28,7 +28,7 @@
 Manages fenced
 .TP
 fence_node
-Calls fence agent, used by lock_gulmd
+Calls the fence agent specified in the configuration file
 
 .SS I/O Fencing agents
 
--- cluster/gfs/man/gfs_mkfs.8	2006/11/29 18:25:50	1.3.2.1
+++ cluster/gfs/man/gfs_mkfs.8	2007/01/16 19:11:30	1.3.2.2
@@ -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-2007 Red Hat, Inc.  All rights reserved.
 
 .TH gfs_mkfs 8
 
@@ -43,9 +43,9 @@
 the filesystem.
 .TP
 \fB-p\fP \fILockProtoName\fR 
-LockProtoName is the name of the  locking  protocol to use.  Acceptable
-locking protocols are \fIlock_dlm\fR, \fIlock_gulm\fR or if you are using GFS
-as a local filesystem (\fB1 node only\fP), you can specify the
+LockProtoName is the name of the  locking  protocol to use.  The locking
+protocol should be \fIlock_dlm\fR for a clustered file system or if you 
+are using GFS as a local filesystem (\fB1 node only\fP), you can specify the
 \fIlock_nolock\fR protocol.
 .TP
 \fB-q\fP
@@ -83,9 +83,3 @@
 "/dev/vg0/mygfs".  It will belong to "mycluster" and register itself
 as wanting locking for "mygfs".  It will use DLM for locking and make
 two journals.
-.TP
-gfs_mkfs -t mycluster:mygfs -p lock_gulm -j 2 /dev/vg0/mygfs
-This will make a Global File System on the block device
-"/dev/vg0/mygfs".  It will belong to "mycluster" and register itself
-as wanting locking for "mygfs".  It will use GULM for locking and make
-two journals.
--- cluster/gfs/man/gfs_mount.8	2005/03/11 21:46:47	1.5
+++ cluster/gfs/man/gfs_mount.8	2007/01/16 19:11:30	1.5.2.1
@@ -1,3 +1,4 @@
+.\"  Copyright (C) 2004-2007 Red Hat, Inc.  All rights reserved.
 .\"  Portions copyright (c) 2001-2003 The OpenGFS Project
 .\"  Portions copyright (c) 2004 ben.m.cahill at intel.com
 .\"
@@ -75,7 +76,7 @@
 The \fILockModuleName\fR must be an exact match of the protocol name presented
 by the lock module when it registers with the lock harness.  Traditionally,
 this matches the .o filename of the lock module, e.g. \fIlock_dlm\fR,
-\fIlock_gulm\fR, or \fIlock_nolock\fR.
+or \fIlock_nolock\fR.
 
 The default lock protocol name is written to disk initially when creating the
 filesystem with \fBgfs_mkfs\fP(8), -p option.  It can be changed on-disk by
@@ -93,8 +94,8 @@
 the inter-node locking system, enabling the mounting of multiple GFS
 filesystems.
 
-The format of \fILockTableName\fR is lock-module-specific.  For lock_gulm
-and lock_dlm, the format is \fIclustername:fsname\fR.  For
+The format of \fILockTableName\fR is lock-module-specific.  For
+lock_dlm, the format is \fIclustername:fsname\fR.  For
 lock_nolock, the field is ignored.
 
 The default cluster/filesystem name is written to disk initially when creating
@@ -106,16 +107,6 @@
 or mount it as a different filesystem name, without changing the on-disk
 default.
 .TP
-\fBhostdata=\fP\fIHostIDInfo\fR
-This field sends host (the computer on which the filesystem is being mounted)
-identity information to the lock module.
-
-The format and behavior of \fIHostIDInfo\fR is lock-module-specific.
-For lock_gulm, it overrides the \fBuname\fP(1) -n network node name
-used as default by lock_gulm.
-
-This field is ignored by \fIlock_dlm\fR and \fIlock_nolock\fR.
-.TP
 \fBlocalcaching\fP
 This flag tells GFS that it is running as a local (not clustered) filesystem,
 so it can turn on some block caching optimizations that can't be used when
@@ -205,7 +196,6 @@
 \fBacl\fP(5) for access control lists,
 \fBlvm\fP(8) for volume management,
 \fBccs\fP(7) for cluster management,
-\fBlock_gulmd\fP(8),
 \fBumount\fP(8),
 \fBinitrd\fP(4).
 
--- cluster/gfs2/man/gfs2_mount.8	2005/09/03 04:07:14	1.4
+++ cluster/gfs2/man/gfs2_mount.8	2007/01/16 19:11:30	1.4.2.1
@@ -1,3 +1,4 @@
+.\"  Copyright (C) 2004-2007 Red Hat, Inc.  All rights reserved.
 .\"  Portions copyright (c) 2001-2003 The OpenGFS2 Project
 .\"  Portions copyright (c) 2004 ben.m.cahill at intel.com
 .\"
@@ -80,7 +81,7 @@
 The \fILockModuleName\fR must be an exact match of the protocol name presented
 by the lock module when it registers with the lock harness.  Traditionally,
 this matches the .o filename of the lock module, e.g. \fIlock_dlm\fR,
-\fIlock_gulm\fR, or \fIlock_nolock\fR.
+or \fIlock_nolock\fR.
 
 The default lock protocol name is written to disk initially when creating the
 filesystem with \fBgfs2_mkfs\fP(8), -p option.  It can be changed on-disk by
@@ -98,8 +99,8 @@
 the inter-node locking system, enabling the mounting of multiple GFS2
 filesystems.
 
-The format of \fILockTableName\fR is lock-module-specific.  For lock_gulm
-and lock_dlm, the format is \fIclustername:fsname\fR.  For
+The format of \fILockTableName\fR is lock-module-specific.  For
+lock_dlm, the format is \fIclustername:fsname\fR.  For
 lock_nolock, the field is ignored.
 
 The default cluster/filesystem name is written to disk initially when creating
@@ -111,17 +112,6 @@
 or mount it as a different filesystem name, without changing the on-disk
 default.
 .TP
-\fBhostdata=\fP\fIHostIDInfo\fR
-This field sends host (the computer on which the filesystem is being mounted)
-identity information to the lock module.
-
-The format and behavior of \fIHostIDInfo\fR is lock-module-specific.
-For lock_gulm, it overrides the \fBuname\fP(1) -n network node name
-used as default by lock_gulm.  For lock_nolock, a \fIHostIDInfo\fR of
-"jid=x" tells GFS to mount journal number x.
-
-This field is ignored by \fIlock_dlm\fR.
-.TP
 \fBlocalcaching\fP
 This flag tells GFS2 that it is running as a local (not clustered) filesystem,
 so it can turn on some block caching optimizations that can't be used when
@@ -215,7 +205,6 @@
 \fBacl\fP(5) for access control lists,
 \fBlvm\fP(8) for volume management,
 \fBccs\fP(7) for cluster management,
-\fBlock_gulmd\fP(8),
 \fBumount\fP(8),
 \fBinitrd\fP(4).

More information about the Cluster-devel mailing list