Red Hat GLOBAL FILE SYSTEM 4.6, Руководство пользователя

Страница: 31 / 62

In this example, the GFS file system on
/dev/vg01/lvol0
is mounted on the
/gfs1
directory.
mount -t gfs /dev/vg01/lvol0 /gfs1
Complete Usage
mount -t gfs BlockDevice MountPoint -o option
The
-o option
argument consists of GFS-specific options (refer to Table 4.2, “GFS-Specific
Mount Options” ) or acceptable standard Linux
mount -o
options, or a combination of both.
Multiple
option
parameters are separated by a comma and no spaces.
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 options (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
allowed to set them (with
setfacl
).
hostdata=HostIDInfo
This field provides host (the computer on which the
file system is being mounted) identity information to
the lock module. The format and behavior of
HostIDInfo
depends on the lock module used. For
lock_gulm
, it overrides the
uname -n
network
node name used as the default value by
lock_gulm
. This field is ignored by the
lock_dlm
and
lock_nolock
lock modules.
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
automatically turns on the
localcaching
and
localflocks
flags.
Tells GFS that it is running as a local file system.
Complete Usage
19