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

Chapter 3. Managing GFS2
node file system. Red Hat will continue to support single-node GFS2 file systems for
existing customers.
Option
acl
data=[ordered|writeback]
ignore_local_fs
Caution: This option should not be used
when GFS2 file systems are shared.
localflocks
Caution: This option should not be used
when GFS2 file systems are shared.
lockproto=LockModuleName
locktable=LockTableName
quota=[off/account/on]
errors=panic|withdraw
Table 3.2. GFS2-Specific Mount Options
14
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).
When data=ordered is set, the user data modified
by a transaction is flushed to the disk before the
transaction is commited to disk. This should prevent
the user from seeing uninitialized blocks in a file after a
crash. When data=writeback mode is set, the user
data is written to the disk at any time after it is dirtied;
this does not provide the same consistency guarantee
as ordered mode, but it should be slightly faster for
some workloads. The default value is ordered mode.
Forces GFS2 to treat the file system as a multihost file
system. By default, using lock_nolock automatically
turns on the localflocks flags.
Tells GFS2 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.
Allows the user to specify which locking table to use
with the file system.
Turns quotas on or off for a file system. Setting the
quotas to be in the account state causes the per UID/
GID usage statistics to be correctly maintained by the
file system; limit and warn values are ignored. The
default value is off.
When errors=panic is specified, file system errors
will cause a kernel panic. The default behavior, which
is the same as specifying errors=withdraw, is for
the system to withdraw from the file system and make
it inaccessible until the next reboot; in some cases the
system may remain running. For information on the
GFS2 withdraw function, see
Withdraw Function".
Section 3.14, "The GFS2