Unmounting A File System - Red Hat GLOBAL FILE SYSTEM 4.5 Manual

Chapter 4. Managing GFS
Option
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
upgrade
Table 4.2. GFS-Specific Mount Options

3. Unmounting a File System

The GFS file system can be unmounted the same way as any Linux file system — by using the
command.
umount
20
Description
GFS can then turn on selected optimization
capabilities that are not available when running in
cluster mode. The
localcaching
automatically turned on by
Tells GFS to let the VFS (virtual file system) layer
do all flock and fcntl. The
automatically turned on by
Allows the user to specify which locking protocol to
use with the file system. If
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.
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.
Note: This option is turned on automatically if
locking is specified; however, you
lock_nolock
can override it by using the
option.
Upgrade the on-disk format of the file system so
that it can be used by newer versions of GFS.
flag is
.
lock_nolock
flag is
localflocks
.
lock_nolock
is not
LockModuleName
ignore_local_fs