Show Table of Contents
3.2. Mounting a GFS2 File System
You should always use Pacemaker to manage the GFS2 file system in a production environment rather than manually mounting the file system with a mount command, as this may cause issues at system shutdown as described in Section 3.3, “Unmounting a GFS2 File System”.
Before you can mount a GFS2 file system, the file system must exist (see Section 3.1, “Creating a GFS2 File System”), the volume where the file system exists must be activated, and the supporting clustering and locking systems must be started (see Configuring and Managing a Red Hat Cluster). After those requirements have been met, you can mount the GFS2 file system as you would any Linux file system.
For proper operation of the GFS2 file system, the
gfs2-utilspackage must be installed on all nodes that mount a GFS2 file system. The
gfs2-utilspackage is part of the Resilient Storage channel.
To manipulate file ACLs, you must mount the file system with the
-o aclmount option. If a file system is mounted without the
-o aclmount option, users are allowed to view ACLs (with
getfacl), but are not allowed to set them (with
Mounting Without ACL Manipulation
Mounting With ACL Manipulation
mount -o acl
- GFS2-specific option to allow manipulating file ACLs.
- Specifies the block device where the GFS2 file system resides.
- Specifies the directory where the GFS2 file system should be mounted.
In this example, the GFS2 file system on
/dev/vg01/lvol0is mounted on the
mount /dev/vg01/lvol0 /mygfs2
-o optionargument consists of GFS2-specific options (see Table 3.2, “GFS2-Specific Mount Options”) or acceptable standard Linux
mount -ooptions, or a combination of both. Multiple
optionparameters are separated by a comma and no spaces.
mountcommand is a Linux system command. In addition to using GFS2-specific options described in this section, you can use other, standard,
mountcommand options (for example,
-r). For information about other Linux
mountcommand options, see the Linux
Table 3.2, “GFS2-Specific Mount Options” describes the available GFS2-specific
-o optionvalues that can be passed to GFS2 at mount time.
This table includes descriptions of options that are used with local file systems only. Note, however, that as of the Red Hat Enterprise Linux 6 release, Red Hat does not support the use of GFS2 as a single-node file system. Red Hat will continue to support single-node GFS2 file systems for mounting snapshots of cluster file systems (for example, for backup purposes).
Table 3.2. GFS2-Specific Mount Options
|Allows manipulating file ACLs. If a file system is mounted without the |
| When |
|Forces GFS2 to treat the file system as a multi-host file system. By default, using |
|Tells GFS2 to let the VFS (virtual file system) layer do all flock and fcntl. The |
|Allows the user to specify which locking protocol to use with the file system. If |
|Allows the user to specify which locking table to use with the file system.|
|Turns quotas on or off for a file system. Setting the quotas to be in the |
|Causes GFS2 to generate "discard" I/O requests for blocks that have been freed. These can be used by suitable hardware to implement thin provisioning and similar schemes.|
| Causes GFS2 to send I/O barriers when flushing the journal. The default value is |
|Sets the number of seconds for which a change in the quota information may sit on one node before being written to the quota file. This is the preferred way to set this parameter. The value is an integer number of seconds greater than zero. The default is 60 seconds. Shorter settings result in faster updates of the lazy quota information and less likelihood of someone exceeding their quota. Longer settings make file system operations involving quotas faster and more efficient.|
| Setting |
| Provides a bound on the maximum percentage change in the |