MOUNT(8)                     System Administration                     MOUNT(8)

NAME
       mount - mount a filesystem

SYNOPSIS
       mount [-h|-V]

       mount [-l] [-t fstype]

       mount -a [-fFnrsvw] [-t fstype] [-O optlist]

       mount [-fnrsvw] [-o options] device|mountpoint

       mount [-fnrsvw] [-t fstype] [-o options] device mountpoint

       mount --bind|--rbind|--move olddir newdir

       mount
       --make-[shared|slave|private|unbindable|rshared|rslave|rprivate|runbindable]
       mountpoint

DESCRIPTION
       All files accessible in a Unix system are arranged in one big tree, the
       file hierarchy, rooted at /. These files can be spread out over several
       devices. The mount command serves to attach the filesystem found on some
       device to the big file tree. Conversely, the umount(8) command will
       detach it again. The filesystem is used to control how data is stored on
       the device or provided in a virtual way by network or other services.

       The standard form of the mount command is:

          mount -t type device dir

       This tells the kernel to attach the filesystem found on device (which is
       of type type) at the directory dir. The option -t type is optional. The
       mount command is usually able to detect a filesystem. The root
       permissions are necessary to mount a filesystem by default. See section
       "Non-superuser mounts" below for more details. The previous contents (if
       any) and owner and mode of dir become invisible, and as long as this
       filesystem remains mounted, the pathname dir refers to the root of the
       filesystem on device.

       If only the directory or the device is given, for example:

          mount /dir

       then mount looks for a mountpoint (and if not found then for a device)
       in the /etc/fstab file. It’s possible to use the --target or --source
       options to avoid ambiguous interpretation of the given argument. For
       example:

          mount --target /mountpoint

       The same filesystem may be mounted more than once, and in some cases
       (e.g., network filesystems) the same filesystem may be mounted on the
       same mountpoint multiple times. The mount command does not implement any
       policy to control this behavior. All behavior is controlled by the
       kernel and it is usually specific to the filesystem driver. The
       exception is --all, in this case already mounted filesystems are ignored
       (see --all below for more details).

   Listing the mounts
       The listing mode is maintained for backward compatibility only.

       For more robust and customizable output use findmnt(8), especially in
       your scripts. Note that control characters in the mountpoint name are
       replaced with '?'.

       The following command lists all mounted filesystems (of type type):

          mount [-l] [-t type]

       The option -l adds labels to this listing. See below.

   Indicating the device and filesystem
       Most devices are indicated by a filename (of a block special device),
       like /dev/sda1, but there are other possibilities. For example, in the
       case of an NFS mount, device may look like knuth.cwi.nl:/dir.

       The device names of disk partitions are unstable; hardware
       reconfiguration, and adding or removing a device can cause changes in
       names. This is the reason why it’s strongly recommended to use
       filesystem or partition identifiers like UUID or LABEL. Currently
       supported identifiers (tags):

       LABEL=label
           Human readable filesystem identifier. See also -L.

       UUID=uuid
           Filesystem universally unique identifier. The format of the UUID is
           usually a series of hex digits separated by hyphens. See also -U.

           Note that mount uses UUIDs as strings. The UUIDs from the command
           line or from fstab(5) are not converted to internal binary
           representation.