Difference between revisions of "Fstab"

__TOC__

__TOC__

<translate>

<translate>

The {{ic|/etc/fstab}} root-owned configuration file is used to define how disk partitions, various other block devices, or remote filesystems should be mounted into the filesystem.

The {{ic|/etc/fstab}} root-owned configuration file is used to define how disk partitions, various other block devices, or remote filesystems should be mounted into the filesystem.

Each filesystem is described in a separate line. These definitions will be converted into systemd mount units dynamically at boot, or when the configuration of the system manager is reloaded.

Each filesystem is described in a separate line. These definitions will be converted into systemd mount units dynamically at boot, or when the configuration of the system manager is reloaded.

The {{ic|mount --all}} command will mount all filesystems mentioned in {{ic|fstab}}, (except for those whose line contains the {{ic|noauto}} keyword). The filesystems are mounted following their order in {{ic|fstab}}. The mount command compares filesystem source and target to detect already mounted filesystems. The kernel table with already mounted filesystems is cached during {{ic|mount --all}}. This means that all duplicated fstab entries will be mounted.

The {{ic|mount --all}} command will mount all filesystems mentioned in {{ic|fstab}}, (except for those whose line contains the {{ic|noauto}} keyword). The filesystems are mounted following their order in {{ic|fstab}}. The mount command compares filesystem source and target to detect already mounted filesystems. The kernel table with already mounted filesystems is cached during {{ic|mount --all}}. This means that all duplicated fstab entries will be mounted.

Each line in the file describes a filesystem, and contain fields (specified in columns) used to provide information about its mountpoint, the options which should be used when mounting it etc. Each field can be separated from one another either by spaces or tabs:

Each line in the file describes a filesystem, and contain fields (specified in columns) used to provide information about its mountpoint, the options which should be used when mounting it etc. Each field can be separated from one another either by spaces or tabs:

  # /etc/fstab: static file system information.

  # /etc/fstab: static file system information.

  UUID=634E43D367B0A4B1                    /media/Data    ntfs-3g noauto,x-systemd.automount,x-systemd.device-timeout=10,rw,inherit,permissions,streams_interface=windows,windows_names,compression,norecover,hide_dot_files,hide_hid_files,big_writes 0 2

  UUID=634E43D367B0A4B1                    /media/Data    ntfs-3g noauto,x-systemd.automount,x-systemd.device-timeout=10,rw,inherit,permissions,streams_interface=windows,windows_names,compression,norecover,hide_dot_files,hide_hid_files,big_writes 0 2

Each column in the above are the fstab "fields" and will be explained in the next section.

Each column in the above are the fstab "fields" and will be explained in the next section.

== Filesystem Specification ==

== Filesystem Specification ==

This field describes one of each of the following:

This field describes one of each of the following:

* swap file or swap partition to be enabled

* swap file or swap partition to be enabled

This field generally takes the form of:

This field generally takes the form of:

* /dev/XdY

* /dev/XdY

As a [https://en.wikipedia.org/wiki/Universally_unique_identifier UUID] is necessarily unique, you will find that this is the default in use on more modern systems whereas a device name and label are only in use on older systems, so we'll concentrate on UUIDs in this tutorial, but know that if you insist on using these order systems, they still work at the time of this writing.

As a [https://en.wikipedia.org/wiki/Universally_unique_identifier UUID] is necessarily unique, you will find that this is the default in use on more modern systems whereas a device name and label are only in use on older systems, so we'll concentrate on UUIDs in this tutorial, but know that if you insist on using these order systems, they still work at the time of this writing.

To get the UUID for all of your devices, execute the command  {{ic|blkid}} elevated to root:

To get the UUID for all of your devices, execute the command  {{ic|blkid}} elevated to root:

and you'll get someting like this:

and you'll get someting like this:

  /dev/sda2: PARTLABEL="Microsoft reserved partition" PARTUUID="b0679b89-007c-441b-88a3-74a39f1f8b2b"

  /dev/sda2: PARTLABEL="Microsoft reserved partition" PARTUUID="b0679b89-007c-441b-88a3-74a39f1f8b2b"

  /dev/sda3: LABEL="WINSYS" BLOCK_SIZE="512" UUID="029873F49873E497" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="f8d444b9-ec60-4ac8-b12a-52448119fad1"

  /dev/sda3: LABEL="WINSYS" BLOCK_SIZE="512" UUID="029873F49873E497" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="f8d444b9-ec60-4ac8-b12a-52448119fad1"

  /dev/sdc1: LABEL="Win-Data" BLOCK_SIZE="512" UUID="634E43D367B0A4B1" TYPE="ntfs" PARTUUID="ca8d0663-6a6e-4b09-a0d7-05b59d109ab1"

  /dev/sdc1: LABEL="Win-Data" BLOCK_SIZE="512" UUID="634E43D367B0A4B1" TYPE="ntfs" PARTUUID="ca8d0663-6a6e-4b09-a0d7-05b59d109ab1"

Any one of the output of {{ic|blkid}} can be used as the first field in the fstab file.

Any one of the output of {{ic|blkid}} can be used as the first field in the fstab file.

E.G. '''all''' of the following lines are valid entries ''for the first line'' of the output of the above example:

E.G. '''all''' of the following lines are valid entries ''for the first line'' of the output of the above example:

  # <file system>                          <mount point>  <type>  <options>                    <dump>  <pass>

  # <file system>                          <mount point>  <type>  <options>                    <dump>  <pass>

  UUID=b86c0cae-3055-4d9e-9e12-1fa1e2cd32d2 /boot/efi      vfat    umask=0077                        0      2

  UUID=b86c0cae-3055-4d9e-9e12-1fa1e2cd32d2 /boot/efi      vfat    umask=0077                        0      2

I.E. only one of the above lines should be present in your fstab file to mount the ESP partition, but any of them will work!

I.E. only one of the above lines should be present in your fstab file to mount the ESP partition, but any of them will work!

''However'' it is strongly recommended to use the UUID as that is '''globally unique!'''.  This means that if your move a disk to another machine, it will keep its UUID and there is no opportunity for surprises like the computer you've moved the existing disk to suddenly:

''However'' it is strongly recommended to use the UUID as that is '''globally unique!'''.  This means that if your move a disk to another machine, it will keep its UUID and there is no opportunity for surprises like the computer you've moved the existing disk to suddenly:

* etc, etc.

* etc, etc.

This field describes the mount point (target) inside your filesystem. For swap partitions, this field should be specified as `none'. If the name of the mount point contains spaces or tabs these can be escaped as `\040' and '\011' respectively.

This field describes the mount point (target) inside your filesystem. For swap partitions, this field should be specified as `none'. If the name of the mount point contains spaces or tabs these can be escaped as `\040' and '\011' respectively.

For more information on the Linux Filesystem Hierarchy standard refer to the [[#See Also]] section, but in a nutshell you should specify an existing directory on your filesystem where you want to mount a partition.

For more information on the Linux Filesystem Hierarchy standard refer to the [[#See Also]] section, but in a nutshell you should specify an existing directory on your filesystem where you want to mount a partition.

In the example {{ic|fstab}} file above, the following line in it's {{ic|blkid}} output:

In the example {{ic|fstab}} file above, the following line in it's {{ic|blkid}} output:

  /dev/sdc1: LABEL="Win-Data" BLOCK_SIZE="512" UUID="634E43D367B0A4B1" TYPE="ntfs" PARTUUID="ca8d0663-6a6e-4b09-a0d7-05b59d109ab1"

  /dev/sdc1: LABEL="Win-Data" BLOCK_SIZE="512" UUID="634E43D367B0A4B1" TYPE="ntfs" PARTUUID="ca8d0663-6a6e-4b09-a0d7-05b59d109ab1"

* has a partition UUID of "ca8d0663-6a6e-4b09-a0d7-05b59d109ab1"

* has a partition UUID of "ca8d0663-6a6e-4b09-a0d7-05b59d109ab1"

and gets mounted on the {{ic|/media/Data}} according to this line:

and gets mounted on the {{ic|/media/Data}} according to this line:

  UUID=634E43D367B0A4B1                    /media/Data    ntfs-3g noauto,x-systemd.automount,x-systemd.device-timeout=10,rw,inherit,permissions,streams_interface=windows,windows_names,compression,norecover,hide_dot_files,hide_hid_files,big_writes 0 2

  UUID=634E43D367B0A4B1                    /media/Data    ntfs-3g noauto,x-systemd.automount,x-systemd.device-timeout=10,rw,inherit,permissions,streams_interface=windows,windows_names,compression,norecover,hide_dot_files,hide_hid_files,big_writes 0 2

This field describes the type of the filesystem. Linux supports many filesystem types: ext4, xfs, btrfs, f2fs, vfat, ntfs-3g (for Windows compatibility), hfsplus (for Mac Compatibility), tmpfs, sysfs, proc, iso9660 (to allow you to mount CD/DVD ISO files as Read-Only directories), udf, squashfs, nfs, cifs, and many more.  

This field describes the type of the filesystem. Linux supports many filesystem types: ext4, xfs, btrfs, f2fs, vfat, ntfs-3g (for Windows compatibility), hfsplus (for Mac Compatibility), tmpfs, sysfs, proc, iso9660 (to allow you to mount CD/DVD ISO files as Read-Only directories), udf, squashfs, nfs, cifs, and many more.  

An entry swap denotes a file or partition to be used for swapping.

An entry swap denotes a file or partition to be used for swapping.

An entry none is useful for bind or move mounts.

An entry none is useful for bind or move mounts.

More than one type may be specified in a comma-separated list.

More than one type may be specified in a comma-separated list.

Using the same example {{ic|fstab}} file and "Win-Data" line as above, {{ic|ntfs-3g}} is the file system we're mounting this one under although the {{ic|blkid}} shows {{ic|ntfs}}.  This is simply because the {{ic|ntfs}} driver is a read-only driver (allowing you to see your Windows files, but not modify them, whereas the {{ic|ntfs-3g}} (for 3rd generation) allows most NTFS options (except encryption) thus also read-write capabilities:

Using the same example {{ic|fstab}} file and "Win-Data" line as above, {{ic|ntfs-3g}} is the file system we're mounting this one under although the {{ic|blkid}} shows {{ic|ntfs}}.  This is simply because the {{ic|ntfs}} driver is a read-only driver (allowing you to see your Windows files, but not modify them, whereas the {{ic|ntfs-3g}} (for 3rd generation) allows most NTFS options (except encryption) thus also read-write capabilities:

This field describes the mount options associated with the filesystem.

This 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 (ro or rw), plus any additional options appropriate to the filesystem type (including performance-tuning options).  

It is formatted as a comma-separated list of options. It contains at least the type of mount (ro or rw), plus any additional options appropriate to the filesystem type (including performance-tuning options).  

Basic filesystem-independent options are:

Basic filesystem-independent options are:

* defaults: use default options: rw, suid, dev, exec, auto, nouser, and async.

* defaults: use default options: rw, suid, dev, exec, auto, nouser, and async.

* nofail: do not report errors for this device if it does not exist.

* nofail: do not report errors for this device if it does not exist.

TBD

TBD

TBD

TBD

TBD

TBD

This field must be 1 or 0 and is used by {{ic|dump}} to determine which filesystems need to be dumped in case of a coredump (=crash). Defaults to zero (don’t dump) if not present.

This field must be 1 or 0 and is used by {{ic|dump}} to determine which filesystems need to be dumped in case of a coredump (=crash). Defaults to zero (don’t dump) if not present.

This field is used by fsck(8) to determine the order in which filesystem checks are done at boot time. The root filesystem ''should be'' specified with a fs_passno of 1. Other filesystems should have a fs_passno 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.

This field is used by fsck(8) to determine the order in which filesystem checks are done at boot time. The root filesystem ''should be'' specified with a fs_passno of 1. Other filesystems should have a fs_passno 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.

Defaults to zero (don’t check the filesystem) if not present.

Defaults to zero (don’t check the filesystem) if not present.

The default setup will automatically `fsck` and `mount` filesystems before starting services that need them to be mounted. For example, systemd automatically makes sure that remote filesystem mounts like NFS or Samba are only started after the network has been set up. Therefore, local and remote filesystem mounts specified in `/etc/fstab` should work out of the box. See {{man 5 systemd.mount}} for details.

The default setup will automatically `fsck` and `mount` filesystems before starting services that need them to be mounted. For example, systemd automatically makes sure that remote filesystem mounts like NFS or Samba are only started after the network has been set up. Therefore, local and remote filesystem mounts specified in `/etc/fstab` should work out of the box. See {{man 5 systemd.mount}} for details.

https://refspecs.linuxfoundation.org/FHS_3.0/index.html

https://refspecs.linuxfoundation.org/FHS_3.0/index.html

</translate>

</translate>

[[Category:Contents Page{{#translation:}}]]

[[Category:Contents Page{{#translation:}}]]