cluster: STABLE3 - gfs: fix binary and manpage names
Fabio M. Di Nitto
fabbione@fedoraproject.org
Fri Jan 23 11:19:00 GMT 2009
Gitweb: http://git.fedorahosted.org/git/cluster.git?p=cluster.git;a=commitdiff;h=a322cc505a5711466138359609707ac4be0401aa
Commit: a322cc505a5711466138359609707ac4be0401aa
Parent: ba6707a6741ea7c33eae5ebfa8fc268342390187
Author: Fabio M. Di Nitto <fdinitto@redhat.com>
AuthorDate: Fri Jan 23 11:14:54 2009 +0100
Committer: Fabio M. Di Nitto <fdinitto@redhat.com>
CommitterDate: Fri Jan 23 12:18:44 2009 +0100
gfs: fix binary and manpage names
Bug: #477072
for way too long we did carrying a non standard naming for our binaries
and manpages.
Signed-off-by: Fabio M. Di Nitto <fdinitto@redhat.com>
---
gfs/gfs_fsck/Makefile | 9 +--
gfs/gfs_mkfs/Makefile | 9 +--
gfs/man/Makefile | 6 +-
gfs/man/fsck.gfs.8 | 59 +++++++++++++++
gfs/man/gfs_fsck.8 | 59 ---------------
gfs/man/gfs_mkfs.8 | 82 ---------------------
gfs/man/gfs_mount.8 | 193 -------------------------------------------------
gfs/man/mkfs.gfs.8 | 82 +++++++++++++++++++++
gfs/man/mount.gfs.8 | 193 +++++++++++++++++++++++++++++++++++++++++++++++++
9 files changed, 341 insertions(+), 351 deletions(-)
diff --git a/gfs/gfs_fsck/Makefile b/gfs/gfs_fsck/Makefile
index 766ad35..af7637d 100644
--- a/gfs/gfs_fsck/Makefile
+++ b/gfs/gfs_fsck/Makefile
@@ -1,10 +1,8 @@
-TARGET1= gfs_fsck
-TARGET2= fsck.gfs
+TARGET1= fsck.gfs
SBINDIRT=$(TARGET1)
-SBINSYMT=$(TARGET2)
-all: ${TARGET1} ${TARGET2}
+all: ${TARGET1}
include ../../make/defines.mk
include $(OBJDIR)/make/cobj.mk
@@ -52,9 +50,6 @@ LDFLAGS += -L${libdir}
${TARGET1}: $(OBJS)
$(CC) -o $@ $^ $(LDFLAGS)
-${TARGET2}: ${TARGET1}
- ln -s ${TARGET1} ${TARGET2}
-
test_block_list: block_list.o bitmap.o log.o test_block_list.o
$(CC) -o $@ $^ $(LDFLAGS)
diff --git a/gfs/gfs_mkfs/Makefile b/gfs/gfs_mkfs/Makefile
index 9174217..39d53a7 100644
--- a/gfs/gfs_mkfs/Makefile
+++ b/gfs/gfs_mkfs/Makefile
@@ -1,10 +1,8 @@
-TARGET1= gfs_mkfs
-TARGET2= mkfs.gfs
+TARGET1= mkfs.gfs
SBINDIRT=$(TARGET1)
-SBINSYMT=$(TARGET2)
-all: depends ${TARGET1} ${TARGET2}
+all: depends ${TARGET1}
include ../../make/defines.mk
include $(OBJDIR)/make/cobj.mk
@@ -33,9 +31,6 @@ LDDEPS += ../libgfs/libgfs.a
${TARGET1}: ${OBJS} ${LDDEPS}
$(CC) -o $@ $^ $(LDFLAGS)
-${TARGET2}: ${TARGET1}
- ln -sf ${TARGET1} ${TARGET2}
-
depends:
$(MAKE) -C ../libgfs all
diff --git a/gfs/man/Makefile b/gfs/man/Makefile
index 3895ff7..7688580 100644
--- a/gfs/man/Makefile
+++ b/gfs/man/Makefile
@@ -1,10 +1,10 @@
TARGET= gfs.8 \
- gfs_mount.8 \
+ mount.gfs.8 \
gfs_edit.8 \
- gfs_fsck.8 \
+ fsck.gfs.8 \
gfs_grow.8 \
gfs_jadd.8 \
- gfs_mkfs.8 \
+ mkfs.gfs.8 \
gfs_quota.8 \
gfs_tool.8
diff --git a/gfs/man/fsck.gfs.8 b/gfs/man/fsck.gfs.8
new file mode 100644
index 0000000..e0894f0
--- /dev/null
+++ b/gfs/man/fsck.gfs.8
@@ -0,0 +1,59 @@
+.TH gfs_fsck 8
+
+.SH NAME
+gfs_fsck - Offline GFS file system checker
+
+.SH SYNOPSIS
+.B gfs_fsck
+[\fIOPTION\fR]... \fIDEVICE\fR
+
+.SH WARNING
+All GFS nodes \fImust\fP have the GFS filesystem unmounted before running
+gfs_fsck. Failure to unmount all nodes may result in filesystem corruption.
+
+.SH DESCRIPTION
+gfs_fsck will check that the GFS file system on a device is structurally valid.
+It should not be run on a mounted file system. If file system corruption is
+detected, it will attempt to repair the file system. There is a limit to what
+gfs_fsck can do. If important file system structures are destroyed, such that
+the checker can not determine what the repairs should be, reparations could
+fail.
+
+GFS is a journaled file system, and as such should be able to repair damages to
+the file system on its own. However, faulty hardware has the ability to write
+incomplete blocks to a file system thereby causing corruption that GFS can not
+fix. The first step to ensuring a healthy file system is the selection of
+reliable hardware (i.e. storage systems that will write complete blocks - even
+in the event of power failure).
+
+.SH OPTIONS
+.TP
+\fB-h\fP
+Help.
+
+This prints out the proper command line usage syntax.
+.TP
+\fB-q\fP
+Quiet.
+.TP
+\fB-n\fP
+No to all questions.
+
+By specifying this option, gfs_fsck will only show the changes that
+would be made, not make any changes to the filesystem.
+.TP
+\fB-V\fP
+Version.
+
+Print out the current version name.
+.TP
+\fB-v\fP
+Verbose operation.
+
+Print more information while running.
+.TP
+\fB-y\fP
+Yes to all questions.
+
+By specifying this option, gfs_fsck will not prompt before making
+changes.
diff --git a/gfs/man/gfs_fsck.8 b/gfs/man/gfs_fsck.8
deleted file mode 100644
index e0894f0..0000000
--- a/gfs/man/gfs_fsck.8
+++ /dev/null
@@ -1,59 +0,0 @@
-.TH gfs_fsck 8
-
-.SH NAME
-gfs_fsck - Offline GFS file system checker
-
-.SH SYNOPSIS
-.B gfs_fsck
-[\fIOPTION\fR]... \fIDEVICE\fR
-
-.SH WARNING
-All GFS nodes \fImust\fP have the GFS filesystem unmounted before running
-gfs_fsck. Failure to unmount all nodes may result in filesystem corruption.
-
-.SH DESCRIPTION
-gfs_fsck will check that the GFS file system on a device is structurally valid.
-It should not be run on a mounted file system. If file system corruption is
-detected, it will attempt to repair the file system. There is a limit to what
-gfs_fsck can do. If important file system structures are destroyed, such that
-the checker can not determine what the repairs should be, reparations could
-fail.
-
-GFS is a journaled file system, and as such should be able to repair damages to
-the file system on its own. However, faulty hardware has the ability to write
-incomplete blocks to a file system thereby causing corruption that GFS can not
-fix. The first step to ensuring a healthy file system is the selection of
-reliable hardware (i.e. storage systems that will write complete blocks - even
-in the event of power failure).
-
-.SH OPTIONS
-.TP
-\fB-h\fP
-Help.
-
-This prints out the proper command line usage syntax.
-.TP
-\fB-q\fP
-Quiet.
-.TP
-\fB-n\fP
-No to all questions.
-
-By specifying this option, gfs_fsck will only show the changes that
-would be made, not make any changes to the filesystem.
-.TP
-\fB-V\fP
-Version.
-
-Print out the current version name.
-.TP
-\fB-v\fP
-Verbose operation.
-
-Print more information while running.
-.TP
-\fB-y\fP
-Yes to all questions.
-
-By specifying this option, gfs_fsck will not prompt before making
-changes.
diff --git a/gfs/man/gfs_mkfs.8 b/gfs/man/gfs_mkfs.8
deleted file mode 100644
index 3da48cb..0000000
--- a/gfs/man/gfs_mkfs.8
+++ /dev/null
@@ -1,82 +0,0 @@
-.TH gfs_mkfs 8
-
-.SH NAME
-gfs_mkfs - Make a GFS filesystem
-
-.SH SYNOPSIS
-.B gfs_mkfs
-[\fIOPTION\fR]... \fIDEVICE\fR
-
-.SH DESCRIPTION
-gfs_mkfs is used to create a Global File System.
-
-.SH OPTIONS
-.TP
-\fB-b\fP \fIBlockSize\fR
-Set the filesystem block size to \fIBlockSize\fR (must be a power of
-two). The minimum block size is 512. The FS block size cannot exceed
-the machine's memory page size. On the most architectures (i386,
-x86_64, s390, s390x), the memory page size is 4096 bytes. On other
-architectures it may be bigger. The default block size is 4096 bytes.
-In general, GFS filesystems should not deviate from the default value.
-.TP
-\fB-D\fP
-Enable debugging output.
-.TP
-\fB-h\fP
-Print out a help message describing available
-options, then exit.
-.TP
-\fB-J\fP \fIMegaBytes\fR
-The size of the journals in Megabytes. The default journal size is
-128 megabytes. The minimum size is 32 megabytes.
-.TP
-\fB-j\fP \fINumber\fR
-The number of journals for gfs_mkfs to create. You need at least one
-journal per machine that will mount the filesystem.
-.TP
-\fB-O\fP
-This option prevents gfs_mkfs from asking for confirmation before writing
-the filesystem.
-.TP
-\fB-p\fP \fILockProtoName\fR
-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
-Be quiet. Don't print anything.
-.TP
-\fB-r\fP \fIMegaBytes\fR
-gfs_mkfs will try to make Resource Groups (RGs) about this big.
-Minimum RG size is 32 MB. Maximum RG size is 2048 MB.
-A large RG size may increase performance on very large file systems.
-If not specified, gfs_mkfs will choose the RG size based on the size
-of the file system: average size file systems will have 256 MB RGs, and
-bigger file systems will have bigger RGs for better performance.
-.TP
-\fB-s\fP \fIBlocks\fR
-Journal segment size in filesystem blocks. This value must be at
-least two and not large enough to produce a segment size greater than
-4MB.
-.TP
-\fB-t\fP \fILockTableName\fR
-The lock table field appropriate to the lock module you're using.
-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 GFS file
-system from others created (1 to 16 characters). Lock_nolock doesn't
-use this field.
-.TP
-\fB-V\fP
-Print program version information, then exit.
-
-.SH EXAMPLE
-.TP
-gfs_mkfs -t mycluster:mygfs -p lock_dlm -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 DLM for locking and make
-two journals.
diff --git a/gfs/man/gfs_mount.8 b/gfs/man/gfs_mount.8
deleted file mode 100644
index e2e842b..0000000
--- a/gfs/man/gfs_mount.8
+++ /dev/null
@@ -1,193 +0,0 @@
-.TH gfs_mount 8
-
-.SH NAME
-gfs_mount - GFS mount options
-
-.SH SYNOPSIS
-.B mount
-[\fIStandardMountOptions\fR] \fB-t\fP gfs \fIDEVICE\fR \fIMOUNTPOINT\fR \fB-o\fP [GFSOption1,GFSOption2,GFSOptionX...]
-
-.SH DESCRIPTION
-GFS may be used as a local (single computer) filesystem, but its real purpose
-is in clusters, where multiple computers (nodes) share a common storage device.
-
-Above is the format typically used to mount a GFS filesystem, using the
-\fBmount\fP(8) command. The \fIdevice\fR may be any block device on which you
-have created a GFS filesystem. Examples include a
-single disk partition (e.g. /dev/sdb3), a loopback device, a device exported
-from another node (e.g. an iSCSI device or a \fBgnbd\fP(8) device), or a
-logical volume (typically comprised of a number of individual disks).
-
-\fIdevice\fR does not necessarily need to match the device name as seen on
-another node in the cluster, nor does it need to be a logical volume. However,
-the use of a cluster-aware volume manager such as CLVM2 (see \fBlvm\fP(8))
-will guarantee that the managed devices are named identically on each node in a
-cluster (for much easier management), and will allow you to configure a very
-large volume from multiple storage units (e.g. disk drives).
-
-\fIdevice\fR must make the entire filesystem storage area visible to the
-computer. That is, you cannot mount different parts of a single filesystem on
-different computers. Each computer must see an entire filesystem. You
-may, however, mount several GFS filesystems if you want to distribute your
-data storage in a controllable way.
-
-\fImountpoint\fR is the same as \fIdir\fR in the \fBmount\fP(8) man page.
-
-This man page describes GFS-specific options that can be passed to the GFS
-file system at mount time, using the \fB-o\fP flag. There are many other
-\fB-o\fP options handled by the generic mount command \fBmount\fP(8).
-However, the options described below are specifically for GFS, and are not
-interpreted by the mount command nor by the kernel's Virtual File System. GFS
-and non-GFS options may be intermingled after the \fB-o\fP, separated by
-commas (but no spaces).
-
-As an alternative to mount command line options, you may send mount
-options to gfs using "gfs_tool margs" (after loading the gfs kernel
-module, but before mounting GFS). For example, you may need to do
-this when working from an initial ramdisk \fBinitrd\fP(4). The
-options are restricted to the ones described on this man page (no
-general \fBmount\fP(8) options will be recognized), must not be
-preceded by -o, and must be separated by commas (no spaces). Example:
-
-# gfs_tool margs "lockproto=lock_nolock,ignore_local_fs"
-
-Options loaded via "gfs_tool margs" have a lifetime of only one GFS
-mount. If you wish to mount another GFS filesystem, you must set
-another group of options with "gfs_tool margs".
-
-If you have trouble mounting GFS, check the syslog (e.g. /var/log/messages)
-for specific error messages.
-
-.SH OPTIONS
-.TP
-\fBlockproto=\fP\fILockModuleName\fR
-This specifies which inter-node lock protocol is used by the GFS filesystem
-for this mount, overriding the default lock protocol name stored in the
-filesystem's on-disk superblock.
-
-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,
-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
-using the \fBgfs_tool\fP(8) utility's \fBsb proto\fP command.
-
-The \fBlockproto\fP mount option should be used only under special
-circumstances in which you want to temporarily use a different lock protocol
-without changing the on-disk default.
-.TP
-\fBlocktable=\fP\fILockTableName\fR
-This specifies the identity of the cluster and of the filesystem for this
-mount, overriding the default cluster/filesystem identify stored in the
-filesystem's on-disk superblock. The cluster/filesystem name is recognized
-globally throughout the cluster, and establishes a unique namespace for
-the inter-node locking system, enabling the mounting of multiple GFS
-filesystems.
-
-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
-the filesystem with \fBgfs_mkfs\fP(8), -t option. It can be changed on-disk
-by using the \fBgfs_tool\fP(8) utility's \fBsb table\fP command.
-
-The \fBlocktable\fP mount option should be used only under special
-circumstances in which you want to mount the filesystem in a different cluster,
-or mount it as a different filesystem name, without changing the on-disk
-default.
-.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
-running in cluster mode.
-
-This is turned on automatically by the lock_nolock module,
-but can be overridden by using the \fBignore_local_fs\fP option.
-.TP
-\fBlocalflocks\fP
-This flag tells GFS that it is running as a local (not clustered) filesystem,
-so it can allow the kernel VFS layer to do all flock and fcntl file locking.
-When running in cluster mode, these file locks require inter-node locks,
-and require the support of GFS. When running locally, better performance
-is achieved by letting VFS handle the whole job.
-
-This is turned on automatically by the lock_nolock module,
-but can be overridden by using the \fBignore_local_fs\fP option.
-.TP
-\fBoopses_ok\fP
-Normally, GFS automatically turns on the "kernel.panic_on_oops"
-sysctl to cause the machine to panic if an oops (an in-kernel
-segfault or GFS assertion failure) happens. An oops on one machine of
-a cluster filesystem can cause the filesystem to stall on all machines
-in the cluster. (Panics don't have this "feature".) By turning on
-"panic_on_oops", GFS tries to make sure the cluster remains in
-operation even if one machine has a problem. There are cases,
-however, where this behavior is not desirable -- debugging being
-the main one. The \fBoopses_ok\fP option causes GFS to leave the
-"panic_on_oops" variable alone so oopses can happen. Use this option
-with care.
-
-This is turned on automatically by the lock_nolock module,
-but can be overridden by using the \fBignore_local_fs\fP option.
-.TP
-\fBignore_local_fs\fP
-By default, using the nolock lock module automatically turns on the
-\fBlocalcaching\fP and \fBlocalflocks\fP optimizations. \fBignore_local_fs\fP
-forces GFS to treat the filesystem as if it were a multihost (clustered)
-filesystem, with \fBlocalcaching\fP and \fBlocalflocks\fP optimizations
-turned off.
-.TP
-\fBupgrade\fP
-This flag tells GFS to upgrade the filesystem's on-disk format to the version
-supported by the current GFS software installation on this computer.
-If you try to mount an old-version disk image, GFS will notify you via a syslog
-message that you need to upgrade. Try mounting again, using the
-\fB-o upgrade\fP option. When upgrading, only one node may mount the GFS
-filesystem.
-.TP
-\fBnum_glockd\fP
-Tunes GFS to alleviate memory pressure when rapidly acquiring many locks (e.g.
-several processes scanning through huge directory trees). GFS' glockd kernel
-daemon cleans up memory for no-longer-needed glocks. Multiple instances
-of the daemon clean up faster than a single instance. The default value is
-one daemon, with a maximum of 32. Since this option was introduced, other
-methods of rapid cleanup have been developed within GFS, so this option may go
-away in the future.
-.TP
-\fBacl\fP
-Enables POSIX Access Control List \fBacl\fP(5) support within GFS.
-.TP
-\fBspectator\fP
-Mount this filesystem using a special form of read-only mount. The mount
-does not use one of the filesystem's journals.
-.TP
-\fBsuiddir\fP
-Sets owner of any newly created file or directory to be that of parent
-directory, if parent directory has S_ISUID permission attribute bit set.
-Sets S_ISUID in any new directory, if its parent directory's S_ISUID is set.
-Strips all execution bits on a new file, if parent directory owner is different
-from owner of process creating the file. Set this option only if you know
-why you are setting it.
-
-.SH LINKS
-.TP 30
-http://sources.redhat.com/cluster
--- home site of GFS
-.TP
-http://www.suse.de/~agruen/acl/linux-acls/
--- good writeup on ACL support in Linux
-
-.SH SEE ALSO
-
-\fBgfs\fP(8),
-\fBmount\fP(8) for general mount options,
-\fBchmod\fP(1) and \fBchmod\fP(2) for access permission flags,
-\fBacl\fP(5) for access control lists,
-\fBlvm\fP(8) for volume management,
-\fBccs\fP(7) for cluster management,
-\fBumount\fP(8),
-\fBinitrd\fP(4).
-
diff --git a/gfs/man/mkfs.gfs.8 b/gfs/man/mkfs.gfs.8
new file mode 100644
index 0000000..3da48cb
--- /dev/null
+++ b/gfs/man/mkfs.gfs.8
@@ -0,0 +1,82 @@
+.TH gfs_mkfs 8
+
+.SH NAME
+gfs_mkfs - Make a GFS filesystem
+
+.SH SYNOPSIS
+.B gfs_mkfs
+[\fIOPTION\fR]... \fIDEVICE\fR
+
+.SH DESCRIPTION
+gfs_mkfs is used to create a Global File System.
+
+.SH OPTIONS
+.TP
+\fB-b\fP \fIBlockSize\fR
+Set the filesystem block size to \fIBlockSize\fR (must be a power of
+two). The minimum block size is 512. The FS block size cannot exceed
+the machine's memory page size. On the most architectures (i386,
+x86_64, s390, s390x), the memory page size is 4096 bytes. On other
+architectures it may be bigger. The default block size is 4096 bytes.
+In general, GFS filesystems should not deviate from the default value.
+.TP
+\fB-D\fP
+Enable debugging output.
+.TP
+\fB-h\fP
+Print out a help message describing available
+options, then exit.
+.TP
+\fB-J\fP \fIMegaBytes\fR
+The size of the journals in Megabytes. The default journal size is
+128 megabytes. The minimum size is 32 megabytes.
+.TP
+\fB-j\fP \fINumber\fR
+The number of journals for gfs_mkfs to create. You need at least one
+journal per machine that will mount the filesystem.
+.TP
+\fB-O\fP
+This option prevents gfs_mkfs from asking for confirmation before writing
+the filesystem.
+.TP
+\fB-p\fP \fILockProtoName\fR
+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
+Be quiet. Don't print anything.
+.TP
+\fB-r\fP \fIMegaBytes\fR
+gfs_mkfs will try to make Resource Groups (RGs) about this big.
+Minimum RG size is 32 MB. Maximum RG size is 2048 MB.
+A large RG size may increase performance on very large file systems.
+If not specified, gfs_mkfs will choose the RG size based on the size
+of the file system: average size file systems will have 256 MB RGs, and
+bigger file systems will have bigger RGs for better performance.
+.TP
+\fB-s\fP \fIBlocks\fR
+Journal segment size in filesystem blocks. This value must be at
+least two and not large enough to produce a segment size greater than
+4MB.
+.TP
+\fB-t\fP \fILockTableName\fR
+The lock table field appropriate to the lock module you're using.
+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 GFS file
+system from others created (1 to 16 characters). Lock_nolock doesn't
+use this field.
+.TP
+\fB-V\fP
+Print program version information, then exit.
+
+.SH EXAMPLE
+.TP
+gfs_mkfs -t mycluster:mygfs -p lock_dlm -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 DLM for locking and make
+two journals.
diff --git a/gfs/man/mount.gfs.8 b/gfs/man/mount.gfs.8
new file mode 100644
index 0000000..e2e842b
--- /dev/null
+++ b/gfs/man/mount.gfs.8
@@ -0,0 +1,193 @@
+.TH gfs_mount 8
+
+.SH NAME
+gfs_mount - GFS mount options
+
+.SH SYNOPSIS
+.B mount
+[\fIStandardMountOptions\fR] \fB-t\fP gfs \fIDEVICE\fR \fIMOUNTPOINT\fR \fB-o\fP [GFSOption1,GFSOption2,GFSOptionX...]
+
+.SH DESCRIPTION
+GFS may be used as a local (single computer) filesystem, but its real purpose
+is in clusters, where multiple computers (nodes) share a common storage device.
+
+Above is the format typically used to mount a GFS filesystem, using the
+\fBmount\fP(8) command. The \fIdevice\fR may be any block device on which you
+have created a GFS filesystem. Examples include a
+single disk partition (e.g. /dev/sdb3), a loopback device, a device exported
+from another node (e.g. an iSCSI device or a \fBgnbd\fP(8) device), or a
+logical volume (typically comprised of a number of individual disks).
+
+\fIdevice\fR does not necessarily need to match the device name as seen on
+another node in the cluster, nor does it need to be a logical volume. However,
+the use of a cluster-aware volume manager such as CLVM2 (see \fBlvm\fP(8))
+will guarantee that the managed devices are named identically on each node in a
+cluster (for much easier management), and will allow you to configure a very
+large volume from multiple storage units (e.g. disk drives).
+
+\fIdevice\fR must make the entire filesystem storage area visible to the
+computer. That is, you cannot mount different parts of a single filesystem on
+different computers. Each computer must see an entire filesystem. You
+may, however, mount several GFS filesystems if you want to distribute your
+data storage in a controllable way.
+
+\fImountpoint\fR is the same as \fIdir\fR in the \fBmount\fP(8) man page.
+
+This man page describes GFS-specific options that can be passed to the GFS
+file system at mount time, using the \fB-o\fP flag. There are many other
+\fB-o\fP options handled by the generic mount command \fBmount\fP(8).
+However, the options described below are specifically for GFS, and are not
+interpreted by the mount command nor by the kernel's Virtual File System. GFS
+and non-GFS options may be intermingled after the \fB-o\fP, separated by
+commas (but no spaces).
+
+As an alternative to mount command line options, you may send mount
+options to gfs using "gfs_tool margs" (after loading the gfs kernel
+module, but before mounting GFS). For example, you may need to do
+this when working from an initial ramdisk \fBinitrd\fP(4). The
+options are restricted to the ones described on this man page (no
+general \fBmount\fP(8) options will be recognized), must not be
+preceded by -o, and must be separated by commas (no spaces). Example:
+
+# gfs_tool margs "lockproto=lock_nolock,ignore_local_fs"
+
+Options loaded via "gfs_tool margs" have a lifetime of only one GFS
+mount. If you wish to mount another GFS filesystem, you must set
+another group of options with "gfs_tool margs".
+
+If you have trouble mounting GFS, check the syslog (e.g. /var/log/messages)
+for specific error messages.
+
+.SH OPTIONS
+.TP
+\fBlockproto=\fP\fILockModuleName\fR
+This specifies which inter-node lock protocol is used by the GFS filesystem
+for this mount, overriding the default lock protocol name stored in the
+filesystem's on-disk superblock.
+
+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,
+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
+using the \fBgfs_tool\fP(8) utility's \fBsb proto\fP command.
+
+The \fBlockproto\fP mount option should be used only under special
+circumstances in which you want to temporarily use a different lock protocol
+without changing the on-disk default.
+.TP
+\fBlocktable=\fP\fILockTableName\fR
+This specifies the identity of the cluster and of the filesystem for this
+mount, overriding the default cluster/filesystem identify stored in the
+filesystem's on-disk superblock. The cluster/filesystem name is recognized
+globally throughout the cluster, and establishes a unique namespace for
+the inter-node locking system, enabling the mounting of multiple GFS
+filesystems.
+
+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
+the filesystem with \fBgfs_mkfs\fP(8), -t option. It can be changed on-disk
+by using the \fBgfs_tool\fP(8) utility's \fBsb table\fP command.
+
+The \fBlocktable\fP mount option should be used only under special
+circumstances in which you want to mount the filesystem in a different cluster,
+or mount it as a different filesystem name, without changing the on-disk
+default.
+.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
+running in cluster mode.
+
+This is turned on automatically by the lock_nolock module,
+but can be overridden by using the \fBignore_local_fs\fP option.
+.TP
+\fBlocalflocks\fP
+This flag tells GFS that it is running as a local (not clustered) filesystem,
+so it can allow the kernel VFS layer to do all flock and fcntl file locking.
+When running in cluster mode, these file locks require inter-node locks,
+and require the support of GFS. When running locally, better performance
+is achieved by letting VFS handle the whole job.
+
+This is turned on automatically by the lock_nolock module,
+but can be overridden by using the \fBignore_local_fs\fP option.
+.TP
+\fBoopses_ok\fP
+Normally, GFS automatically turns on the "kernel.panic_on_oops"
+sysctl to cause the machine to panic if an oops (an in-kernel
+segfault or GFS assertion failure) happens. An oops on one machine of
+a cluster filesystem can cause the filesystem to stall on all machines
+in the cluster. (Panics don't have this "feature".) By turning on
+"panic_on_oops", GFS tries to make sure the cluster remains in
+operation even if one machine has a problem. There are cases,
+however, where this behavior is not desirable -- debugging being
+the main one. The \fBoopses_ok\fP option causes GFS to leave the
+"panic_on_oops" variable alone so oopses can happen. Use this option
+with care.
+
+This is turned on automatically by the lock_nolock module,
+but can be overridden by using the \fBignore_local_fs\fP option.
+.TP
+\fBignore_local_fs\fP
+By default, using the nolock lock module automatically turns on the
+\fBlocalcaching\fP and \fBlocalflocks\fP optimizations. \fBignore_local_fs\fP
+forces GFS to treat the filesystem as if it were a multihost (clustered)
+filesystem, with \fBlocalcaching\fP and \fBlocalflocks\fP optimizations
+turned off.
+.TP
+\fBupgrade\fP
+This flag tells GFS to upgrade the filesystem's on-disk format to the version
+supported by the current GFS software installation on this computer.
+If you try to mount an old-version disk image, GFS will notify you via a syslog
+message that you need to upgrade. Try mounting again, using the
+\fB-o upgrade\fP option. When upgrading, only one node may mount the GFS
+filesystem.
+.TP
+\fBnum_glockd\fP
+Tunes GFS to alleviate memory pressure when rapidly acquiring many locks (e.g.
+several processes scanning through huge directory trees). GFS' glockd kernel
+daemon cleans up memory for no-longer-needed glocks. Multiple instances
+of the daemon clean up faster than a single instance. The default value is
+one daemon, with a maximum of 32. Since this option was introduced, other
+methods of rapid cleanup have been developed within GFS, so this option may go
+away in the future.
+.TP
+\fBacl\fP
+Enables POSIX Access Control List \fBacl\fP(5) support within GFS.
+.TP
+\fBspectator\fP
+Mount this filesystem using a special form of read-only mount. The mount
+does not use one of the filesystem's journals.
+.TP
+\fBsuiddir\fP
+Sets owner of any newly created file or directory to be that of parent
+directory, if parent directory has S_ISUID permission attribute bit set.
+Sets S_ISUID in any new directory, if its parent directory's S_ISUID is set.
+Strips all execution bits on a new file, if parent directory owner is different
+from owner of process creating the file. Set this option only if you know
+why you are setting it.
+
+.SH LINKS
+.TP 30
+http://sources.redhat.com/cluster
+-- home site of GFS
+.TP
+http://www.suse.de/~agruen/acl/linux-acls/
+-- good writeup on ACL support in Linux
+
+.SH SEE ALSO
+
+\fBgfs\fP(8),
+\fBmount\fP(8) for general mount options,
+\fBchmod\fP(1) and \fBchmod\fP(2) for access permission flags,
+\fBacl\fP(5) for access control lists,
+\fBlvm\fP(8) for volume management,
+\fBccs\fP(7) for cluster management,
+\fBumount\fP(8),
+\fBinitrd\fP(4).
+
More information about the Cluster-cvs
mailing list