Installation guide

Note
The mount command is a Linux system command. In addition to using GFS-specific
options described in this section, you can use other, standard, mount command op-
tions (for example, -r). For information about other Linux mount command options,
see the Linux mount man page.
Table 4.2, “GFS-Specific Mount Options” describes the available GFS-specific -o option values
that can be passed to GFS at mount time.
Option Description
acl 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 al-
lowed to set them (with setfacl).
ignore_local_fs
Caution: This option should not be used
when GFS file systems are shared.
Forces GFS to treat the file system as a multihost
file system. By default, using lock_nolock automat-
ically turns on the localcaching and localflocks
flags.
localcaching
Caution: This option should not be used
when GFS file systems are shared.
Tells GFS that it is running as a local file system.
GFS can then turn on selected optimization capab-
ilities that are not available when running in cluster
mode. The localcaching flag is automatically
turned on by lock_nolock.
localflocks
Caution: This option should not be used
when GFS file systems are shared.
Tells GFS to let the VFS (virtual file system) layer
do all flock and fcntl. The localflocks flag is auto-
matically turned on by lock_nolock.
lockproto=LockModuleName 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.
locktable=LockTableName Allows the user to specify which locking table to
use with the file system.
oopses_ok
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 minim-
izes 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 de-
Complete Usage
17