Before you can mount a GFS file system, the file system must exist (refer to Section 5.1 Making a File System), the volume where the file system exists must be activated, and the supporting clustering and locking systems must be started (refer to Chapter 4 Getting Started and Red Hat Cluster Suite Configuring and Managing a Cluster). After those requirements have been met, you can mount the GFS file system as you would any Linux file system.
To manipulate file ACLs, you must mount the file system with the -o acl mount option. If a file system is mounted without the -o acl mount option, users are allowed to view ACLs (with getfacl), but are not allowed to set them (with setfacl).
Mounting Without ACL Manipulation
mount -t gfs BlockDevice MountPoint
Mounting With ACL Manipulation
mount -t gfs -o acl BlockDevice MountPoint
GFS-specific option to allow manipulating file ACLs.
Specifies the block device where the GFS file system resides.
Specifies the directory where the GFS file system should be mounted.
In this example, the GFS file system on /dev/vg01/lvol0 is mounted on the /gfs1 directory.
mount -t gfs /dev/vg01/lvol0 /gfs1
mount -t gfs BlockDevice MountPoint -o option
The -o option consists of GFS-specific options (refer to Table 5-2) or acceptable standard Linux mount -o options, or a combination of both. Multiple option parameters are separated by a comma and no spaces.
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 5-2 describes the available GFS-specific -o option values that can be passed to GFS at mount time.
|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.|
|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. GFS can then turn on selected optimization capabilities that are not available when running in cluster mode. The localcaching flag is automatically turned on by lock_nolock.|
|Tells GFS to let the VFS (virtual file system) layer do all flock and fcntl. The localflocks flag is automatically 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.|
|upgrade||Upgrade the on-disk format of the file system so that it can be used by newer versions of GFS.|
Table 5-2. GFS-Specific Mount Options