FSTAB(5)\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 File Formats\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 FSTAB(5)<\/p>\n
NAME<\/p>\n
fstab – static information about the filesystems<\/p>\n
SYNOPSIS<\/p>\n
\/etc\/fstab<\/p>\n
DESCRIPTION<\/p>\n
The file fstab contains descriptive information about the various
\nfile systems.\u00a0 fstab is only read by programs, and not written; it is
\nthe duty of the system administrator to properly create and maintain
\nthis file.\u00a0 Each filesystem is described on a separate line; fields
\non each line are separated by tabs or spaces.\u00a0 Lines starting with
\n‘#’ are comments, blank lines are ignored. The order of records in
\nfstab is important because fsck(8), mount(8), and umount(8)
\nsequentially iterate through fstab doing their thing.<\/p>\n
The first field (fs_spec).
\nThis field describes the block special device or remote
\nfilesystem to be mounted.<\/p>\n
For ordinary mounts it will hold (a link to) a block special
\ndevice node (as created by mknod(8)) for the device to be
\nmounted, like `\/dev\/cdrom’ or `\/dev\/sdb7′.\u00a0 For NFS mounts one
\nwill have <host>:<dir>, e.g., `knuth.aeb.nl:\/’.\u00a0 For procfs,
\nuse `proc’.<\/p>\n
Instead of giving the device explicitly, one may indicate the
\nfilesystem that is to be mounted by its UUID or LABEL (cf.
\ne2label(8) or xfs_admin(8)), writing LABEL=<label> or
\nUUID=<uuid>, e.g., `LABEL=Boot’ or `UUID=3e6be9de-8139-11d1\u2010
\n-9106-a43f08d823a6′.<\/p>\n
It’s also possible to use PARTUUID= and PARTLABEL=. These
\npartitions identifiers are supported for example for GUID
\nPartition Table (GPT).<\/p>\n
See mount(8), blkid(8) or lsblk(8) for more details about
\ndevices identifiers.<\/p>\n
Note that mount(8) uses UUIDs as strings. The string
\nrepresentation of the UUID should be based on lower case
\ncharacters.<\/p>\n
The second field (fs_file).
\nThis field describes the mount point for the filesystem.\u00a0 For
\nswap partitions, this field should be specified as `none’. If
\nthe name of the mount point contains spaces these can be
\nescaped as `\\040′.<\/p>\n
The third field (fs_vfstype).
\nThis field describes the type of the filesystem.\u00a0 Linux
\nsupports lots of filesystem types, the most common are ext2,
\next3, ext4, xfs, btrfs, vfat, sysfs, proc, nfs and cifs. For
\nmore details, see mount(8).<\/p>\n
An entry swap denotes a file or partition to be used for
\nswapping, cf. swapon(8).\u00a0 An entry none is useful for bind or
\nmove mounts.<\/p>\n
More than one type may be specified in a comma-separated list.<\/p>\n
mount(8) and umount(8) support filesystem subtypes.\u00a0 The
\nsubtype is defined by ‘.subtype’ suffix.\u00a0 For example
\n‘fuse.sshfs’. It’s recommended to use subtype notation rather
\nthan add any prefix to the first fstab field (for example
\n‘sshfs#example.com’ is deprecated).<\/p>\n
The fourth field (fs_mntops).
\nThis field describes the mount options associated with the
\nfilesystem.<\/p>\n
It is formatted as a comma separated list of options.\u00a0 It
\ncontains at least the type of mount plus any additional
\noptions appropriate to the filesystem type. For documentation
\non the available mount options, see mount(8).\u00a0 For
\ndocumentation on the available swap options, see swapon(8).<\/p>\n
Basic file system independent options are:<\/p>\n
defaults
\nuse default options: rw, suid, dev, exec, auto, nouser,
\nand async.<\/p>\n
noauto do not mount when “mount -a” is given (e.g., at boot
\ntime)<\/p>\n
user\u00a0\u00a0 allow a user to mount<\/p>\n
owner\u00a0 allow device owner to mount<\/p>\n
comment
\nor x-<name> for use by fstab-maintaining programs<\/p>\n
nofail do not report errors for this device if it does not
\nexist.<\/p>\n
The fifth field (fs_freq).
\nThis field is used for these filesystems by the dump(8)
\ncommand to determine which filesystems need to be dumped.\u00a0 If
\nthe fifth field is not present, a value of zero is returned
\nand dump will assume that the filesystem does not need to be
\ndumped.<\/p>\n
The sixth field (fs_passno).
\nThis field is used by the fsck(8) program to determine the
\norder in which filesystem checks are done at reboot time.\u00a0 The
\nroot filesystem should be specified with a fs_passno of 1, and
\nother filesystems should have a fs_passno of 2.\u00a0 Filesystems
\nwithin a drive will be checked sequentially, but filesystems
\non different drives will be checked at the same time to
\nutilize parallelism available in the hardware.\u00a0 If the sixth
\nfield is not present or zero, a value of zero is returned and
\nfsck will assume that the filesystem does not need to be
\nchecked.<\/p>\n
NOTES<\/p>\n
The proper way to read records from fstab is to use the routines
\ngetmntent(3) or libmount.<\/p>\n
The keyword ignore as filesystem type (3rd field) is not more
\nsupported by the pure libmount based mount utility (since util-linux
\nv2.22).<\/p>\n
FILES<\/p>\n
\/etc\/fstab, <fstab.h><\/p>\n
SEE ALSO<\/p>\n
findmnt(8), mount(8), swapon(8), fs(5), getmntent(3)<\/p>\n
HISTORY<\/p>\n
The ancestor of this fstab file format appeared in 4.0BSD.<\/p>\n
AVAILABILITY<\/p>\n
This man page is part of the util-linux package and is available from
\nftp:\/\/ftp.kernel.org\/pub\/linux\/utils\/util-linux\/.<\/p>\n
COLOPHON<\/p>\n
This page is part of the util-linux (a random collection of Linux
\nutilities) project.\u00a0 Information about the project can be found at
\n\u27e8https:\/\/www.kernel.org\/pub\/linux\/utils\/util-linux\/\u27e9.\u00a0 If you have a
\nbug report for this manual page, send it to
\nutil-linux@vger.kernel.org.\u00a0 This page was obtained from the
\nproject’s upstream Git repository
\n(git:\/\/git.kernel.org\/pub\/scm\/utils\/util-linux\/util-linux.git) on
\n2014-12-30.\u00a0 If you discover any rendering problems in this HTML ver\u2010
\nsion of the page, or you believe there is a better or more up-to-date
\nsource for the page, or you have corrections or improvements to the
\ninformation in this COLOPHON (which is not part of the original man\u2010
\nual page), send a mail to\u00a0man-pages@man7.org<\/p>\n
util-linux\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 August 2010\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 FSTAB(5)<\/p>\n","protected":false},"excerpt":{"rendered":"
FSTAB(5)\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 File Formats\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 FSTAB(5) NAME fstab – static information about the filesystems SYNOPSIS \/etc\/fstab DESCRIPTION The file fstab contains descriptive information about the various file systems.\u00a0 fstab is only read by programs, and not written; it is the duty of the system administrator to properly create and maintain this file.\u00a0 Each filesystem is described on […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_sitemap_exclude":false,"_sitemap_priority":"","_sitemap_frequency":"","footnotes":""},"categories":[8],"tags":[],"class_list":["post-320","post","type-post","status-publish","format-standard","hentry","category-shell"],"a3_pvc":{"activated":false,"total_views":0,"today_views":0},"_links":{"self":[{"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=\/wp\/v2\/posts\/320","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=320"}],"version-history":[{"count":0,"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=\/wp\/v2\/posts\/320\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=320"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=320"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=320"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}