4.2. Mounting a File System
cman) has not been started produces the following error message:
mount -t gfs2 -o noatime /dev/mapper/mpathap1 /mntgfs_controld join connect error: Connection refused error mounting lockproto lock_dlm
-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
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.
/dev/vg01/lvol0is mounted on the
mount /dev/vg01/lvol0 /mygfs2
-o optionargument consists of GFS2-specific options (see Table 4.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
-o optionvalues that can be passed to GFS2 at mount time.
Table 4.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 multihost 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 |