contains descriptive information about the various file systems.
is only read by programs, and not written; it is the duty of the system
administrator to properly create and maintain this file. Each filesystem
is described on a separate line; fields on each line are separated by tabs
or spaces. Lines starting with ‘#’ are comments. blank lines are ignored. The
order of records in
is important because
sequentially iterate through
doing their thing.
The first field,
describes the block special device or
remote filesystem to be mounted.
For ordinary mounts it will hold (a link to) a block special
device node (as created by
for the device to be mounted, like `/dev/cdrom’ or `/dev/sdb7′.
For NFS mounts one will have <host>:<dir>, e.g., `knuth.aeb.nl:/’.
For procfs, use `proc’.
Instead of giving the device explicitly, one may indicate
the (ext2 or xfs) filesystem that is to be mounted by its UUID or
volume label (cf.
writing LABEL=<label> or UUID=<uuid>,
e.g., `LABEL=Boot’ or `UUID=3e6be9de-8139-11d1-9106-a43f08d823a6′.
This will make the system more robust: adding or removing a SCSI disk
changes the disk device name but not the filesystem volume label.
The second field,
describes the mount point for the filesystem. For swap partitions, this
field should be specified as `none’. If the name of the mount point
contains spaces these can be escaped as ` 40′.
The third field,
describes the type of the filesystem. Linux supports lots
of filesystem types, such as
and possibly others. For more details, see
For the filesystems currently supported by the running kernel, see
denotes a file or partition to be used
for swapping, cf.
causes the line to be ignored. This is useful
to show disk partitions which are currently unused.
is useful for bind or move mounts.
support filesystem subtypes. The subtype is defined by ‘.subtype’ suffix. For
example ‘fuse.sshfs’. It’s recommended to use subtype notation rather than add
any prefix to the first fstab field (for example ‘sshfs#example.com’ is
The fourth field,
describes the mount options associated with the filesystem.
It is formatted as a comma separated list of options. It contains at least
the type of mount plus any additional options appropriate to the filesystem
type. For documentation on the available options for non-nfs file systems,
For documentation on all nfs-specific options have a look at
Common for all types of file system are the options “noauto”
(do not mount when "mount -a" is given, e.g., at boot time), “user”
(allow a user to mount), and “owner”
(allow device owner to mount), and “comment”
(e.g., for use by fstab-maintaining programs).
The “owner” and “comment” options are Linux-specific.
For more details, see
The fifth field,
is used for these filesystems by the
command to determine which filesystems need to be dumped. If the fifth
field is not present, a value of zero is returned and
will assume that the filesystem does not need to be dumped.
The sixth field,
is used by the
program to determine the order in which filesystem checks are done at
reboot time. The root filesystem should be specified with a
of 1, and other filesystems should have a
of 2. Filesystems within a drive will be checked sequentially, but
filesystems on different drives will be checked at the same time to utilize
parallelism available in the hardware. If the sixth field is not present
or zero, a value of zero is returned and
will assume that the filesystem does not need to be checked.
The proper way to read records from
is to use the routines
The ancestor of this
file format appeared in 4.0BSD.
This man page is part of the util-linux-ng package and is available from