Red Hat ENTERPRISE LINUX 5 - GLOBAL FILE SYSTEM Manual page 24

Chapter 3. Managing GFS
(for example, -r). For information about other Linux mount command options, see the
Linux mount man page.
Table 3.2, "GFS-Specific Mount Options"
can be passed to GFS at mount time.
Note
This table includes descriptions of options that are used with local file systems only For
the RHEL 5.5 release and later Red Hat does not support the use of GFS as a single-
node file system. Red Hat will continue to support single-node GFS file systems for
existing customers.
Option
acl
ignore_local_fs
Caution: This option should not be used
when GFS file systems are shared.
localcaching
Caution: This option should not be used
when GFS file systems are shared.
localflocks
Caution: This option should not be used
when GFS file systems are shared.
lockproto=LockModuleName
locktable=LockTableName
oopses_ok
14
describes the available GFS-specific -o option values that
Description
Allows manipulating file ACLs. If a file system is
mounted without the acl mount option, users are
allowed to view ACLs (with getfacl), but are not
allowed to set them (with setfacl).
Forces GFS to treat the file system as a multihost file
system. By default, using lock_nolock automatically
turns on the localcaching and localflocks flags.
Tells GFS that it is running as a local file system. GFS
can then turn on selected optimization capabilities
that are not available when running in cluster mode.
The localcaching flag is automatically turned on by
lock_nolock.
Tells GFS to let the VFS (virtual file system) layer do all
flock and fcntl. The localflocks flag is automatically
turned on by lock_nolock.
Allows the user to specify which locking protocol to
use with the file system. If LockModuleName is not
specified, the locking protocol name is read from the
file system superblock.
For a clustered file system, allows the user to specify
which locking table to use with the file system.
This option allows a GFS node to not panic when an
oops occurs. (By default, a GFS node panics when
an oops occurs, causing the file system used by that
node to stall for other GFS nodes.) A GFS node not
panicking when an oops occurs minimizes the failure
on other GFS nodes using the file system that the
failed node is using. There may be circumstances
where you do not want to use this option — for
example, when you need more detailed troubleshooting
information. Use this option with care.