mount, umount - mount and dismount file systems
S
\bSY
\bYN
\bNO
\bOP
\bPS
\bSI
\bIS
\bS
m
\bmo
\bou
\bun
\bnt
\bt [ -
\b-a
\baf
\bfr
\brw
\bwu
\bu ] [ -
\b-t
\bt nfs | ufs | external_type ]
m
\bmo
\bou
\bun
\bnt
\bt [ -
\b-f
\bfr
\brw
\bwu
\bu ] special | node
m
\bmo
\bou
\bun
\bnt
\bt [ -
\b-f
\bfr
\brw
\bwu
\bu ] [ -
\b-t
\bt nfs | ufs | external_type ] [ -
\b-o
\bo
u
\bum
\bmo
\bou
\bun
\bnt
\bt [ -
\b-a
\baf
\bf ] [ -
\b-t
\bt nfs | ufs | external_type ]
u
\bum
\bmo
\bou
\bun
\bnt
\bt [ -
\b-f
\bf ] special | node
D
\bDE
\bES
\bSC
\bCR
\bRI
\bIP
\bPT
\bTI
\bIO
\bON
\bN
_
\bM_
\bo_
\bu_
\bn_
\bt announces to the system that a removable file system
is present on the block device _
\bs_
\bp_
\be_
\bc_
\bi_
\ba_
\bl or the remote node
``rhost:path''. The file _
\bn_
\bo_
\bd_
\be must exist already and it must
be a directory. It becomes the name of the newly mounted
root. The optional arguments -_
\br and -_
\bw indicate that the
file system is to be mounted read-only or read-write,
respectively. If either _
\bs_
\bp_
\be_
\bc_
\bi_
\ba_
\bl or _
\bf_
\bi_
\bl_
\be are not provided,
the appropriate information is taken from the _
\bf_
\bs_
\bt_
\ba_
\bb file.
The -_
\bf option causes everything to be done except for the
actual system call; if it's not obvious, this ``fakes''
mounting the file system. This option is useful in conjunc-
tion with the -_
\bv flag to determine what the _
\bm_
\bo_
\bu_
\bn_
\bt command is
The optional argument -_
\bt can be used to indicate the file
system type. The type u
\buf
\bfs
\bs is the default. If the type is
not one of the internally known types, mount will attempt to
execute a program in /
\b/s
\bsb
\bbi
\bin
\bn/
\b/m
\bmo
\bou
\bun
\bnt
\bt_
\b_X
\bXX
\bXX
\bX where X
\bXX
\bXX
\bX is replaced
by the type name. The standard mount options (see below)
are parsed and passed to external program via the -_
\bF option
as a decimal number. Any additional options specific to the
program can be passed as a comma separated list; these
options are distinguished by starting with a - (dash).
Those options that take a value are specified using the syn-
tax -option=value. For example, the mount command:
mount -t mfs -o nosuid,-N,-s=4000 /dev/dk0b /tmp
causes mount to attempt to execute:
/sbin/mount_mfs -F 8 -N -s 4000 /dev/dk0b /tmp
Options are specified by a -_
\bo argument followed by a comma
separated string of options. The following options apply to
any file system that is being mounted:
noexec Do not allow execution of any binaries on the
mounted file system. This options is useful for
a server that has file systems containing
binaries for architectures other than its own.
nosuid Do not allow set-user-identifier or set-group-
identifier bits to take effect.
nodev Do not interpret character or block special dev-
ices on the file system. This options is useful
for a server that has file systems containing
special devices for architectures other than its
synchronous All I/O to the file system should be done syn-
The -_
\bu flag indicates that the status of an already mounted
file system should be changed. Any of the options above may
be changed; also a file system can be changed from read-only
to read-write. The set of options is determined by first
extracting the options for the file system from the _
\bf_
\bs_
\bt_
\ba_
\bb
table, then applying any options specified by the -_
\bo argu-
ment, and finally applying the -_
\br or -_
\bw option.
The following list can be used to override the defaults for
hard I/O system calls will retry until the server
soft I/O system calls will fail and return errno
after _
\br_
\be_
\bt_
\br_
\ba_
\bn_
\bs request retransmissions
spongy Soft semantics for the stat, lookup, fsstat,
readlink and readdir filesystem operations and
hard semantics for the others. This option is
meant to be similar to hard, except that
processes will not be hung forever when they
trip over mount points to dead servers.
bg If the first mount request times out, do retries
intr I/O system calls can be interrupted.
noconn Do not connect the socket. Used for UDP servers
that send replies from a socket other than the
tcp Use TCP transport instead of UDP.
rsize=# Set read size to # bytes.
wsize=# Set write size to # bytes.
retry=# Set mount retry count to #.
retrans=# Set retransmission count for nfs rpc's to #.
timeo=# Set initial nfs timeout to # in 0.1 sec inter-
_
\bU_
\bm_
\bo_
\bu_
\bn_
\bt announces to the system that the removable file sys-
tem _
\bn_
\bo_
\bd_
\be or whatever removable file system was previously
mounted on device _
\bs_
\bp_
\be_
\bc_
\bi_
\ba_
\bl should be removed. If the -_
\bf
option is specified for _
\bu_
\bm_
\bo_
\bu_
\bn_
\bt, the file system is forcibly
unmounted. Active special devices continue to work, but all
other files return errors if further accesses are attempted.
The root file system cannot be forcibly unmounted.
If the -_
\ba option is present for either _
\bm_
\bo_
\bu_
\bn_
\bt or _
\bu_
\bm_
\bo_
\bu_
\bn_
\bt, all
of the file systems described in _
\bf_
\bs_
\bt_
\ba_
\bb are mounted or
unmounted. The optional argument -_
\bt can be used to indicate
that the actions should only be taken on filesystems of the
specified type. More than one type may be specified in a
comma separated list. The list of filesystem types can be
prefixed with ``no'' to specify the filesystem types on
which no action should be taken. For example, the mount
mounts all filesystems except those of type NFS and MFS.
The system maintains a list of currently mounted file sys-
tems. If invoked without an argument, _
\bm_
\bo_
\bu_
\bn_
\bt prints the
list. The optional argument -_
\bt can be used to indicate that
only filesystems of the specified type should be listed.
More than one type may be specified in a comma separated
list. The list of filesystem types can be prefixed with
``no'' to indicate the types of filesystems to be excluded
Physically write-protected and magnetic tape file systems
must be mounted read-only or errors will occur when access
times are updated, whether or not any explicit write is
/etc/fstab file system table
S
\bSE
\bEE
\bE A
\bAL
\bLS
\bSO
\bO
mount(2), unmount(2), fstab(5)
Mounting garbaged file systems will crash the system.
Mounting a root directory on a non-directory makes some
apparently good path names invalid.
projects / unix-history / blob