Makes a file system available for use.
mount [ -f ] [ -n Node ] [ -o Options ] [ -p ] [ -r ] [ -v VfsName ] [ -t Type | [ Device | Node:Directory ] Directory | all | -a ] [-V [generic_options] special_mount_points ]
The mount command instructs the operating system to make a file system available for use at a specified location (the mount point). In addition, you can use the mount command to build other file trees made up of directory and file mounts. The mount command mounts a file system expressed as a device using the Device or Node:Directory parameter on the directory specified by the Directory parameter. After the mount command has finished, the directory specified becomes the root directory of the newly mounted file system.
Only users with root authority or are members of the system group and have write access to the mount point can issue file or directory mounts. The file or directory may be a symbolic link. The mount command uses the real user ID, not the effective user ID, to determine if the user has appropriate access. System group members can issue device mounts, provided they have write access to the mount point and those mounts specified in the /etc/filesystems file. Users with root user authority can issue any mount command.
Users can mount a device provided they belong to the system group and have appropriate access. When mounting a device, the mount command uses the Device parameter as the name of the block device and the Directory parameter as the directory on which to mount the file system.
If you enter the mount command without flags, the command displays the following information for the mounted file systems:
If you specify only the Directory parameter, the mount command takes it to be the name of the directory or file on which a file system, directory, or file is usually mounted (as defined in the /etc/filesystems file). The mount command looks up the associated device, directory, or file and mounts it. This is the most convenient way of using the mount command, because it does not require you to remember what is normally mounted on a directory or file. You can also specify only the device. In this case, the command obtains the mount point from the /etc/filesystems file.
The /etc/filesystems file should include a stanza for each mountable file system, directory, or file. This stanza should specify at least the name of the file system and either the device on which it resides or the directory name. If the stanza includes a mount attribute, the mount command uses the associated values. It recognizes five values for the mount attributes: automatic, true, false, removable, and readonly.
The mount all command causes all file systems with the mount=true attribute to be mounted in their normal places. This command is typically used during system initialization, and the corresponding mounts are referred to as automatic mounts.
The CacheFS-specific version of the mount command mounts a cached file system; if necessary, it NFS-mounts its back file system. It also provides a number of CacheFS-specific options for controlling the caching process.
To mount a CacheFS file system, use the mount command with the -V flag followed by the argument. The following mount flags are available:
The following arguments to the -o flag are specifically for CacheFS mounts. Use commas to separate multiple options.
Note: The backfstype argument must be
|The file system type of the back file system (for example, nfs).
|Specifies where the back file system is already mounted. If this argument is not supplied, CacheFS determines a mount point for the back file system. The back file system must be read-only.
|The name of the cache directory.
|ID is a string specifying a particular instance of a cache. If you do not specify a cache ID, CacheFS will construct one.
|write-around | non-shared
|Write modes for CacheFS. The write-around mode (the default) handles writes the same as NFS does; that is, writes are made to the back file system, and the affected file is purged from the cache. You can use the non-shared mode when you are sure that no one else will be writing to the cached file system.
|Disables cache consistency checking. By default, periodic consistency checking is enabled. Specify noconst only when you know that the back file system will not be modified. Trying to perform cache consistency check using cfsadmin-s will result in error. demandconst and noconst are mutually exclusive.
|Causes the front file system to interpret the mode bits used for access checking instead or having the back file system verify access permissions. Do not use this argument with secure NFS.
|Purge any cached information for the specified file system.
|rw | ro
|Read-write (default) or read-only.
|suid | nosuid
|Allow (default) or disallow set-uid execution
|Specifies that cached attributes are held for at least n seconds after file modification. After n seconds, CacheFS checks to see if the file modification time on the back file system has changed. If it has, all information about the file is purged from the cache and new data is retrieved from the back file system. The default value is 30 seconds.
|Specifies that cached attributes are held for no more than n seconds after file modification. After n seconds, all file information is purged from the cache. The default value is 30 seconds.
|Specifies that cached attributes are held for at least n seconds after directory update. After n seconds, CacheFS checks to see if the directory modification time on the back file system has changed. If it has, all information about the directory is purged from the cache and new data is retrieved from the back file system. The default value is 30 seconds.
|Sets acregmin, acregmax, acdirmin, and acdirmax to n.
You can use the File Systems application in Web-based System Manager (wsm) to run this command. You could also use the System Management Interface Tool (SMIT) smit mount fast path to run this command.
Note: If the mount command encounters a Journaled File System or Enhanced Journaled File System which was not unmounted before reboot, a replay of any JFS or JFS2 log records is attempted. In order to move a compatible JFS filesystem to a system running an earlier release of the operating system, the filesystem must always be unmounted cleanly prior to its movement. Failure to unmount first may result in an incompatible JFS log device. If the movement results in an unknown log device, the filesystem should be returned to the system running the latter operating system release, and fsck should be run on the filesystem.
JFS is POWER-based platform only, and JFS2 is common to both platforms.
|Mounts all file systems in the /etc/filesystems file with stanzas that contain the true mount attribute.
|Same as the -a flag.
|Requests a forced mount during system initialization to enable mounting over the root file system.
|Specifies the remote node that holds the directory to be mounted.
File System Specific
|Specifies options. Options you enter on the command line should be
separated only by a comma, not a comma and a space. The following file-
system-specific options do not apply to all virtual-file-system types:
NFS Specific Options
|Mounts a file system as a removable file system. While open files are on it, a removable mounted file system behaves the same as a normally mounted file system. However, when no files are open (and no process has a current directory on the file system), all of the file system disk buffers in the file system are written to the medium, and the operating system forgets the structure of the file system.
|Mounts a file system as a read-only file system, regardless of its previous specification in the /etc/filesystems file.
|Mounts all stanzas in the /etc/filesystems file that contain the type=Type attribute and are not mounted. The Type parameter specifies the name of the group.
|Specifies that the file system is defined by the VfsName parameter in the /etc/vfs file.
This command produces output similar to the following:
node mounted mounted vfs date options over ---- ------- --------- --- ------------ ------- --------- /dev/hd0 / jfs Dec 17 08:04 rw, log =/dev/hd8 /dev/hd3 /tmp jfs Dec 17 08:04 rw, log =/dev/hd8 /dev/hd1 /home jfs Dec 17 08:06 rw, log =/dev/hd8 /dev/hd2 /usr jfs Dec 17 08:06 rw, log =/dev/hd8 sue /home/local/src /usr/code nfs Dec 17 08:06 ro, log =/dev/hd8
For each file system, the mount command lists the node name, the device name, the name under which it is mounted, the virtual-file-system type, the date and time it was mounted, and its options.
mount -V cachefs -o backfstype=nfs,backpath=/usr/abc, cachedir=/cache1 server1:/user2 /xyz
The lines similar to the following appear in the /etc/mnttab file after the mount command is executed:
server1:/user2 /usr/abc nfs /usr/abc /cache1/xyz cachefs backfstype=nfs
|Lists the known file systems and defines their characteristics.
|Contains descriptions of virtual-file-system types.
The nfso command, umount command.
The mntctl subroutine, mount subroutine, umount subroutine.
The filesystems file, vfs file.
For information on installing the Web-based System Manager, see Chapter 2: Installation and System Requirements in AIX 5L Version 5.1 Web-based System Manager Administration Guide.
Mounting Overview and System Management Interface Tool (SMIT): Overview in AIX 5L Version 5.1 System Management Concepts: Operating System and Devices.