Table of Contents
Advertisement
Chapter 9. Managing GFS
Option
acl
-o
hostdata=nodename
lockproto=LockModuleName
locktable=LockTableName
upgrade
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.
Table 9-2. GFS-Specific Mount Options
9.3. Unmounting a File System
The GFS file system can be unmounted the same way as any Linux file system.
Note
The
command is a Linux system command. Information about this command can be found in
umount
the Linux
umount
command man pages.
Description
Allows manipulating file ACLs. If a file system is
mounted without the
allowed to view ACLs (with
allowed to set them (with
LOCK_GULM file systems use this information to set
the local node name, overriding the usual selection of
node name from
uname -n
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.
Upgrade the on-disk format of the file system so that
it can be used by newer versions of GFS.
Forces GFS to treat the file system as a multihost file
system. By default, using LOCK_NOLOCK
automatically turns on the
flags.
localflocks
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
by LOCK_NOLOCK.
Tells GFS to let the VFS (virtual file system) layer do
all flock and fcntl. The
automatically turned on by LOCK_NOLOCK.
mount option, users are
acl
-o
), but are not
getfacl
).
setfacl
.
localcaching
flag is automatically turned on
flag is
localflocks
93
and
Advertisement
Table of Contents
