NAME
mount, umount - mount and unmount file system
SYNOPSIS
/etc/mount [fsname directory [-frv] [-s|-u] [-o options] [-t type]] /etc/mount -a [-fv] [-s|-u]
/etc/mount [-p] [-l|-L] [-s|-u]
/etc/umount [-v] [-s] fsname
/etc/umount [-v] [-s] directory
/etc/umount -a [-v] [-s] [-h host]] [-t type]]
DESCRIPTION
mount announces to the system that a removable file system is to be attached to the file tree at directory. directory must already exist, and becomes the name of the root of the newly mounted file system. directory must be given as an absolute path name and cannot be a context-dependent file (see cdf(4)). fsname must be either the name of a special file or of the form host:path. If fsname is of the form host:path, the file system type is assumed to be nfs (see -t option below).
These commands maintain a table of mounted devices in /etc/mnttab. If invoked with no arguments, mount prints the table.
umount announces to the system that the removable file system fsname previously mounted on directory directory is to be unmounted. Either the file system name or the directory where the file system is mounted can be specified.
In the HP Clustered Environment, only NFS and HFS file systems can be mounted and unmounted from client nodes. See Networking Features below.
Options (mount)
mount recognizes the following options. Options are positionindependent and can occur in any order.
The following options are valid only on hfs type file systems:
Options (umount)
umount recognizes the following options. Options are positionindependent and can occur in any order.
acregmin=3, acregmax=60, acdirmin=30, acdirmax=60. actimeo has no default; it sets acregmin, acregmax, acdirmin, and acdirmax to the value specified.
Hewlett-Packard Company - 4 - HP-UX Release 9.0: August 1992
The bg option causes mount to run in the background if the server's mount daemon does not respond. mount attempts each request retry=n times before giving up. Once the file system is mounted, each NFS request made in the kernel waits timeo=n tenths of a second for a response. If no response arrives, the timeout is multiplied by 2 and the request is retransmitted. When retrans=n retransmissions have been sent with no reply, a soft mounted file system returns an error on the request and a hard mounted file system retries the request. By default, the retry requests for a hard mounted file system can be interrupted. If the nointr option is specified, retry requests for a hard mounted file system are not interruptable which means that retry requests continue until successful. File systems that are mounted rw (read-write) should use the hard option. The number of bytes in a read or write request can be set with the rsize and wsize options. The devs option allows access to devices attached to the NFS client via device files located on the mounted NFS file system. The nodevs option denies access to devices attached to the NFS client by causing attempts to read or write to NFS device files to return an error.
File Attributes
The attribute cache retains file attributes on the client. Attributes for a file are assigned a time to be flushed. If the file is modified before the flush time, the flush time is extended by the time since the last modification (under the assumption that files that changed recently are likely to change soon). There is a minimum and maximum flush time extension for regular files and for directories. Setting actimeo=n extends flush time by n seconds for both regular files and directories.
NFS Mounts in HP Clustered Environment:
If an NFS mount is made from the server node or any of the client nodes, the NFS file system is accessible from all nodes. If the mount is made from a client node and the client node is rebooted, the mount continues to function normally for all remaining nodes, and will function for the rebooted client without remounting the NFS file system.
DIAGNOSTICS
Attempting to mount a currently mounted non-nfs volume under another name results in an error.
umount complains if the special file is not mounted or if it is busy. The file system is busy if it contains an open file or some user's working directory.
Cascaded distributed mounts (mounts whose mount point resides on another client node's locally mounted disk) are not supported.
EXAMPLES
Mount a local disk:
Hewlett-Packard Company - 5 - HP-UX Release 9.0: August 1992
mount /dev/dsk/c0d0s4 /usr
NFS:
Mount a remote file system:
mount serv:/usr/src /usr/src -t nfs
Same as above:
mount serv:/usr/src /usr/src
Same as above but with a soft mount; the file system is mounted readonly:
mount serv:/usr/src /usr/src -o soft,ro
WARNINGS
A directory or file must be exported by exportfs before it is NFS mounted (see exportfs(1M)).
Some degree of validation is done on the file system. However, it is generally unwise to mount file systems that are defective, corrupt, or of unknown origin.
Mounting CD-ROM media on a cnode that is not the cluster server is not supported.
AUTHOR
mount was developed by HP, AT&T, the University of California, Berkeley, and Sun Microsystems.
Hewlett-Packard Company - 6 - HP-UX Release 9.0: August 1992