Difference between revisions of "Fstab"

From ArchWiki
Jump to: navigation, search
m (added boot debuggin link, minor syntax fix)
(External devices: rm specific version clutter)
 
(148 intermediate revisions by 47 users not shown)
Line 1: Line 1:
{{Lowercase_title}}
+
{{Lowercase title}}
 
[[Category:File systems]]
 
[[Category:File systems]]
 
[[Category:Boot process]]
 
[[Category:Boot process]]
{{i18n|Fstab}}
+
[[ar:Fstab]]
 +
[[es:Fstab]]
 +
[[hu:Fstab]]
 +
[[it:Fstab]]
 +
[[ja:Fstab]]
 +
[[ro:Fstab]]
 +
[[ru:Fstab]]
 +
[[zh-CN:Fstab]]
 +
[[zh-TW:Fstab]]
 +
{{Related articles start}}
 +
{{Related|Persistent block device naming}}
 +
{{Related|File systems}}
 +
{{Related|Mount}}
 +
{{Related|tmpfs}}
 +
{{Related|swap}}
 +
{{Related articles end}}
  
{{Article summary start}}
+
The [[Wikipedia:Fstab|/etc/fstab]] file can be used to define how disk partitions, various other block devices, or remote filesystems should be mounted into the filesystem.
{{Article summary text|This article explains how to configure and use fstab.}}
+
{{Article summary heading|Related}}
+
{{Article summary wiki|udev}}
+
{{Article summary end}}
+
  
The {{ic|/etc/fstab}} file contains static filesystem information.  It defines how storage devices and partitions are to be mounted and integrated into the overall system. It is read by the {{ic|mount}} command to determine which options to use when mounting a specific device or partition.
+
Each filesystem is described in a separate line. These definitions will be converted into [[systemd]] mount units dynamically at boot, and when the configuration of the system manager is reloaded. 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 {{ic|/etc/fstab}} should work out of the box. See {{ic|man 5 systemd.mount}} for details.
 +
 
 +
The {{ic|mount}} command will use fstab, if just one of either directory or device is given, to fill in the value for the other parameter. When doing so, mount options which are listed in fstab will also be used.
  
 
== File example ==
 
== File example ==
  
 
A simple {{ic|/etc/fstab}}, using kernel name descriptors:
 
A simple {{ic|/etc/fstab}}, using kernel name descriptors:
 +
 
{{hc|/etc/fstab|
 
{{hc|/etc/fstab|
 
# <file system>        <dir>        <type>    <options>            <dump> <pass>
 
# <file system>        <dir>        <type>    <options>            <dump> <pass>
tmpfs                  /tmp          tmpfs    nodev,nosuid          0      0
 
 
/dev/sda1              /            ext4      defaults,noatime      0      1
 
/dev/sda1              /            ext4      defaults,noatime      0      1
 
/dev/sda2              none          swap      defaults              0      0
 
/dev/sda2              none          swap      defaults              0      0
/dev/sda3              /home        ext4      defaults,noatime      0      2
+
/dev/sda3              /home        ext4      defaults,noatime      0      2}}
}}
+
  
 
== Field definitions ==
 
== Field definitions ==
The {{ic|/etc/fstab}} file contains the following fields separated by a space or tab:
 
  
<file system> <dir> <type> <options> <dump> <pass>
+
Each line in the {{ic|/etc/fstab}} file contains the following fields separated by spaces or tabs:
  
* '''<file system>''' - the partition or storage device to be mounted.
+
''file_system''   ''dir''   ''type''   ''options''   ''dump''   ''pass''
* '''<dir>''' - the mountpoint where <file system> is mounted to.
+
* '''<type>''' - the file system type of the partition or storage device to be mounted. Many different file systems are supported: {{ic|ext2, ext3, reiserfs, xfs, jfs, smbfs, iso9660, vfat, ntfs, swap}} and {{ic|auto}}. The {{ic|auto}} type lets the mount command guess what type of file system is used. This is useful for removable devices such as cdroms and dvds.
+
* '''<options>''' - the options of the filesystem to be used. Note that some options are filesystem specific. Some of the most common options are:
+
  
:* {{ic|auto}} - Mount automatically at boot, or when the command {{ic|mount -a}} is issued.
+
;''file system''
:* {{ic|noauto}} - Mount only when you tell it to.
+
:The partition or storage device to be mounted.
:* {{ic|exec}} - Allow execution of binaries on the filesystem.
+
;''dir''
:* {{ic|noexec}} - Disallow execution of binaries on the filesystem.
+
:The mountpoint where <file system> is mounted to.
:* {{ic|ro}} - Mount the filesystem read-only.
+
;''type''
:* {{ic|rw}} - Mount the filesystem read-write.
+
:The file system type of the partition or storage device to be mounted. Many different file systems are supported: {{ic|ext2}}, {{ic|ext3}}, {{ic|ext4}}, {{ic|btrfs}}, {{ic|reiserfs}}, {{ic|xfs}}, {{ic|jfs}}, {{ic|smbfs}}, {{ic|iso9660}}, {{ic|vfat}}, {{ic|ntfs}}, {{ic|swap}} and {{ic|auto}}. The {{ic|auto}} type lets the mount command guess what type of file system is used. This is useful for optical media (CD/DVD).
:* {{ic|user}} - Allow any user to mount the filesystem. This automatically implies {{ic|noexec, nosuid, nodev}}, unless overridden.
+
;''options''
:* {{ic|users}} - Allow any user in the users group to mount the filesystem.
+
:Mount options of the filesystem to be used. See the [http://man7.org/linux/man-pages/man8/mount.8.html#FILESYSTEM-INDEPENDENT_MOUNT%20OPTIONS mount man page]. Please note that some options are specific to filesystems; to discover them see below in the aforementioned mount man page.
:* {{ic|nouser}} - Allow only root to mount the filesystem.
+
;''dump''
:* {{ic|owner}} - Allow the owner of device to mount.
+
:Used by the dump utility to decide when to make a backup. Dump checks the entry and uses the number to decide if a file system should be backed up. Possible entries are 0 and 1. If 0, dump will ignore the file system; if 1, dump will make a backup. Most users will not have dump installed, so they should put 0 for the ''dump'' entry.
:* {{ic|sync}} - I/O should be done synchronously.
+
;''pass''
:* {{ic|async}} - I/O should be done asynchronously.
+
:Used by [[fsck]] to decide which order filesystems are to be checked. Possible entries are 0, 1 and 2. The root file system should have the highest priority 1 (unless its type is [[btrfs]], in which case this field should be 0) - all other file systems you want to have checked should have a 2. File systems with a value 0 will not be checked by the fsck utility.
:* {{ic|dev}} - Interpret block special devices on the filesystem.
+
:* {{ic|nodev}} - Don't interpret block special devices on the filesystem.
+
:* {{ic|suid}} - Allow the operation of suid, and sgid bits. They are mostly used to allow users on a computer system to execute binary executables with temporarily elevated privileges in order to perform a specific task.
+
:* {{ic|nosuid}} - Block the operation of suid, and sgid bits.
+
:* {{ic|noatime}} - Don't update inode access times on the filesystem. Can help performance (see [[#atime_options|atime options]]).
+
:* {{ic|nodiratime}} - Do not update directory inode access times on the filesystem. Can help performance (see [[#atime_options|atime options]]).
+
:* {{ic|relatime}} - Update inode access times relative to modify or change time. Access time is only updated if the previous access time was earlier than the current modify or change time. (Similar to noatime, but doesn't break mutt or other applications that need to know if a file has been read since the last time it was modified.) Can help performance (see [[#atime_options|atime options]]).
+
:* {{ic|flush}} - The {{ic|vfat}} option to flush data more often, thus making copy dialogs or progress bars to stay up until all data is written.
+
:* {{ic|defaults}} - the default mount options for the filesystem to be used. The default options for {{ic|ext3}} are: {{ic|rw, suid, dev, exec, auto, nouser, async}}.
+
 
+
* '''<dump>''' - used by the dump utility to decide when to make a backup. Dump checks the entry and uses the number to decide if a file system should be backed up. Possible entries are 0 and 1. If 0, dump will ignore the file system; if 1, dump will make a backup. Most users will not have dump installed, so they should put 0 for the <dump> entry.
+
 
+
* '''<pass>''' - used by [[fsck]] to decide which order filesystems are to be checked. Possible entries are 0, 1 and 2. The root file system should have the highest priority 1 - all other file systems you want to have checked should have a 2. File systems with a value 0 will not be checked by the fsck utility.
+
  
 
== Identifying filesystems ==
 
== Identifying filesystems ==
  
There are three ways to identify a partition or storage device in {{ic|/etc/fstab}}: by its kernel name descriptor, label or UUID. The advantage of using UUIDs or labels is that they are not dependent on the disks order. This is useful if the storage device order in the BIOS is changed, or if you switch the storage device cabling. Also, sometimes the BIOS may occasionally change the order of storage devices. Read more about this in the [[Persistent_block_device_naming|persistent block device naming]] article.
+
There are different ways to identify filesystems that will be mounted. {{ic|/etc/fstab}} does support several methods: kernel name descriptor, label or UUID, and GPT labels and UUID for GPT disks. UUID must be privileged over kernel name descriptors and labels. See [[Persistent block device naming]] for more explanations. It is recommended to read that article first before continuing with this article.
  
=== Kernel name ===
+
In this section, we will describe how to mount filesystems using all the mount methods available via examples. The output of the commands {{ic|lsblk -f}} and {{ic|blkid}} used in the following examples are available in the article [[Persistent block device naming]]. If you have not read that article yet, please read it now.
  
You can get the kernel name descriptors using {{ic|fdisk -l}}. The kernel names are listed in the first row:
+
=== Kernel name descriptors ===
  
{{hc|# fdisk -l|<nowiki>
+
Run {{ic|lsblk -f}} to list the partitions and prefix the values in the ''NAME'' column with {{ic|/dev/}}.
...
+
Device Boot      Start        End      Blocks  Id  System
+
/dev/sda1  *          1        2550    20482843+  b  W95 FAT32
+
/dev/sda2            2551        5100    20482875  83  Linux
+
/dev/sda3            5101        7650    20482875  83  Linux
+
/dev/sda4            7651      121601  915311407+  5  Extended
+
/dev/sda5            7651      10200    20482843+  83  Linux
+
/dev/sda6          10201      17849    61440561  83  Linux
+
/dev/sda7          17850      18104    2048256  82  Linux swap / Solaris
+
/dev/sda8          18105      18113      72261  83  Linux
+
/dev/sda9          18114      121601  831267328+  7  HPFS/NTFS
+
...</nowiki>}}
+
  
See the [[Fstab#File_example|file example]].
+
{{hc|/etc/fstab|<nowiki>
 +
# <file system> <dir> <type> <options>                                                                                            <dump> <pass>
 +
/dev/sda1      /boot vfat  rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0      2
 +
/dev/sda2      /    ext4  rw,relatime,discard,data=ordered                                                                    0      1
 +
/dev/sda3      /home ext4  rw,relatime,discard,data=ordered                                                                    0      2
 +
/dev/sda4      none  swap  defaults                                                                                            0      0
 +
</nowiki>}}
  
=== Label ===
+
=== Labels ===
  
In order to use labels, the devices or partitions must have unambiguous labels. Labels should be unambiguous to prevent any possible conflicts - each label should be unique. To label a device or partition, see [[Persistent_block_device_naming|this]] article. To list all devices and partitions with their labels, you can use the command {{ic|blkid}}. In {{ic|/etc/fstab}} you prefix the device label with {{ic|LABEL<nowiki>=</nowiki>}} :
+
Run {{ic|lsblk -f}} to list the partitions, and prefix the values in the ''LABEL'' column with {{ic|1=LABEL=}}:
  
 
{{hc|/etc/fstab|<nowiki>
 
{{hc|/etc/fstab|<nowiki>
# <file system>       <dir>         <type>   <options>             <dump> <pass>
+
# <file system> <dir> <type> <options>                                                                                           <dump> <pass>
 +
LABEL=EFI      /boot vfat  rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0      2
 +
LABEL=SYSTEM    /    ext4  rw,relatime,discard,data=ordered                                                                    0      1
 +
LABEL=DATA      /home ext4  rw,relatime,discard,data=ordered                                                                    0      2
 +
LABEL=SWAP      none  swap  defaults                                                                                            0      0
 +
</nowiki>}}
  
tmpfs                  /tmp          tmpfs    nodev,nosuid          0      0
+
{{Note|If any of your fields contains spaces, see [[#Filepath spaces]].}}
+
 
LABEL=Arch_Linux      /             ext4     defaults,noatime      0      1
+
=== UUIDs ===
LABEL=Arch_Swap        none         swap     defaults             0      0
+
 
 +
Run {{ic|lsblk -f}} to list the partitions, and prefix the values in the ''UUID'' column with {{ic|1=UUID=}}:
 +
 
 +
{{hc|/etc/fstab|<nowiki>
 +
# <file system>                          <dir> <type> <options>                                                                                            <dump> <pass>
 +
UUID=CBB6-24F2                            /boot vfat  rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0      2
 +
UUID=0a3407de-014b-458b-b5c1-848e92a327a3 /     ext4   rw,relatime,discard,data=ordered                                                                    0      1
 +
UUID=b411dc99-f0a0-4c87-9e05-184977be8539 /home ext4  rw,relatime,discard,data=ordered                                                                    0      2
 +
UUID=f9fe0b69-a280-415d-a03a-a32752370dee none swap   defaults                                                                                             0      0
 
</nowiki>}}
 
</nowiki>}}
  
=== UUID ===
+
{{Tip|If you would like to return just the UUID of a specific partition:
 +
$ lsblk -no UUID /dev/sda2}}
  
All partitions and devices have a unique UUID. They are generated by the make-filesystem utilities ({{ic|mkfs.*}}) when you create the filesystem. To list all devices and partitions with their UUID, you can also use {{ic|blkid}}. In {{ic|/etc/fstab}} you prefix the device UUID with {{ic|UUID<nowiki>=</nowiki>}} :
+
=== GPT labels ===
 +
Run {{ic|blkid}} to list the partitions, and use the ''PARTLABEL'' values without the quotes:
  
 
{{hc|/etc/fstab|<nowiki>
 
{{hc|/etc/fstab|<nowiki>
# <file system>                           <dir>         <type>   <options>             <dump> <pass>
+
# <file system>                     <dir> <type> <options>                                                                                           <dump> <pass>
 +
PARTLABEL=EFI\040SYSTEM\040PARTITION /boot vfat  rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0      2
 +
PARTLABEL=GNU/LINUX                  /    ext4  rw,relatime,discard,data=ordered                                                                    0      1
 +
PARTLABEL=HOME                      /home ext4  rw,relatime,discard,data=ordered                                                                    0      2
 +
PARTLABEL=SWAP                      none  swap  defaults                                                                                            0      0
 +
</nowiki>}}
  
tmpfs                                    /tmp          tmpfs    nodev,nosuid          0      0
+
{{Note|If any of your fields contains spaces, see [[#Filepath spaces]].}}
+
 
UUID=24f28fc6-717e-4bcd-a5f7-32b959024e26 /    ext4             defaults,noatime      0      1
+
=== GPT UUIDs ===
UUID=03ec5dd3-45c0-4f95-a363-61ff321a09ff /home ext4             defaults,noatime      0      2
+
 
UUID=4209c845-f495-4c43-8a03-5363dd433153 none  swap             defaults             0      0
+
Run {{ic|blkid}} to list the partitions, and use the ''PARTUUID'' values without the quotes:
 +
 
 +
{{hc|/etc/fstab|<nowiki>
 +
# <file system>                              <dir> <type> <options>                                                                                            <dump> <pass>
 +
PARTUUID=d0d0d110-0a71-4ed6-936a-304969ea36af /boot vfat  rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0      2
 +
PARTUUID=98a81274-10f7-40db-872a-03df048df366 /    ext4   rw,relatime,discard,data=ordered                                                                    0      1
 +
PARTUUID=7280201c-fc5d-40f2-a9b2-466611d3d49e /home ext4   rw,relatime,discard,data=ordered                                                                    0      2
 +
PARTUUID=039b6c1c-7553-4455-9537-1befbc9fbc5b none  swap   defaults                                                                                             0      0
 
</nowiki>}}
 
</nowiki>}}
  
 
== Tips and tricks ==
 
== Tips and tricks ==
  
=== Swap UUID ===
+
=== Automount with systemd ===
In case your swap partition doesn't have an UUID, you can add it manually. This happens when the UUID of the swap is not shown with the {{ic|blkid}} command. Here are some steps to assign a UUID to your swap:
+
  
Identify the swap partition:
+
If you have a large {{ic|/home}} partition, it might be better to allow services that do not depend on {{ic|/home}} to start while {{ic|/home}} is checked by ''fsck''. This can be achieved by adding the following options to the {{ic|/etc/fstab}} entry of your {{ic|/home}} partition:
# swapon -s
+
  
Disable the swap:
+
  noauto,x-systemd.automount
  # swapoff /dev/sda7
+
  
Recreate the swap with a new UUID assigned to it:
+
This will fsck and mount {{ic|/home}} when it is first accessed, and the kernel will buffer all file access to {{ic|/home}} until it is ready.
# mkswap -U random /dev/sda7
+
  
Activate the swap:
+
{{Note|This will make your {{ic|/home}} filesystem type {{ic|autofs}}, which is ignored by [[mlocate]] by default. The speedup of automounting {{ic|/home}} may not be more than a second or two, depending on your system, so this trick may not be worth it.}}
# swapon /dev/sda7
+
  
=== Filepath spaces ===
+
The same applies to remote filesystem mounts. If you want them to be mounted only upon access, you will need to use the {{ic|noauto,x-systemd.automount}} parameters. In addition, you can use the {{ic|1=x-systemd.device-timeout=#}} option to specify a timeout in case the network resource is not available.
  
You can use the escape character "\" followed by the 3 digit octal code "040" to emulate spaces in a path:
+
{{Note|1=If you intend to use the {{ic|exec}} flag with automount, you should remove the {{ic|user}} flag for it to work properly as found in the course of a [https://bugzilla.redhat.com/show_bug.cgi?id=769636 Fedora Bug Report]}}
  
{{hc|/etc/fstab|<nowiki>.....
+
If you have encrypted filesystems with keyfiles, you can also add the {{ic|noauto}} parameter to the corresponding entries in {{ic|/etc/crypttab}}. ''systemd'' will then not open the encrypted device on boot, but instead wait until it is actually accessed and then automatically open it with the specified keyfile before mounting it. This might save a few seconds on boot if you are using an encrypted RAID device for example, because systemd does not have to wait for the device to become available. For example:
/dev/sda7                /home/username/Camera\040Pictures  ext4  defaults,noatime      0  2
+
UUID=7D4500B3071E18B2    /media/100\040GB\040(Storage)      ntfs  defaults,noatime,user  0  0
+
.....</nowiki>}}
+
  
===External devices===
+
{{hc|/etc/crypttab|
External devices that are to be mounted when present but ignored if absent may require the {{ic|nofail}} option. This prevents errors being reported at boot.
+
data /dev/md0 /root/key noauto}}
{{hc|/etc/fstab|<nowiki>.....
+
/dev/sdg1    /media/backup    jfs    defaults,nofail    0  2
+
.....</nowiki>}}
+
  
=== atime options ===
+
You may also specify an idle timeout for a mount with the {{ic|x-systemd.idle-timeout}} flag.  For example:
  
The use of {{ic|noatime}}, {{ic|nodiratime}} or {{ic|relatime}} can help disk performance for ext2, ext3, and ext4 filesystems. Linux by default keeps a record (writes to the disk) every time it reads from the disk {{ic|atime}}.  This was more purposeful when Linux was being used for servers; it doesn't have much value for desktop use. The worst thing about the default {{ic|atime}} option is that even reading a file from the page cache (reading from memory instead of the disk) will still result in a disk write! Using the {{ic|noatime}} option fully disables writing file access times to the disk every time you read a file.  This works well for almost all applications, except for a rare few like [[Mutt]] that need the such information.  For mutt, you should only use the {{ic|relatime}} option. Using the {{ic|relatime}} option enables the writing of file access times only when the file is being modified (unlike {{ic|noatime}} where the file access time will never be changed and will be older than the modification time). The {{ic|nodiratime}} option disables the writing of file access times only for directories while other files still get access times written. The best compromise might be the use of {{ic|relatime}} in which case programs like [[Mutt]] will continue to work, but you'll still have a performance boost because files will not get access times updated unless they are modified.
+
  noauto,x-systemd.automount,x-systemd.idle-timeout=1min
  
{{Note|{{ic|noatime}} already includes {{ic|nodiratime}}. You do not need to specify both options.[http://lwn.net/Articles/244941/ ]}}
+
This will make systemd unmount the mount after it has been idle for 1 minute.
  
===tmpfs===
+
=== External devices ===
[[Wikipedia:Tmpfs|tmpfs]] is a temporary filesystem that resides in memory and/or your swap partition(s), depending on how much you fill it up. Mounting directories as tmpfs can be an effective way of speeding up accesses to their files, or to ensure that their contents are automatically cleared upon reboot.
+
  
Some directories where tmpfs is commonly used are [http://www.pathname.com/fhs/2.2/fhs-3.15.html /tmp], [http://www.pathname.com/fhs/2.2/fhs-5.9.html /var/lock] and [http://www.pathname.com/fhs/2.2/fhs-5.13.html /var/run]. Do NOT use it on [http://www.pathname.com/fhs/2.2/fhs-5.15.html /var/tmp], because that folder is meant for temporary files that are preserved across reboots.
+
External devices that are to be mounted when present but ignored if absent may require the {{ic|nofail}} option. This prevents errors being reported at boot. For example:  
  
By default, a tmpfs partition has its maximum size set to half your total RAM, but this can be customized. Note that the actual memory/swap consumption depends on how much you fill it up, as tmpfs partitions do not consume any memory until it is actually needed.
+
{{hc|/etc/fstab|2=
 +
/dev/sdg1        /media/backup    jfs    defaults,nofail,x-systemd.device-timeout=1    0  2}}
  
To use tmpfs for {{ic|/tmp}}, add this line to {{ic|/etc/fstab}}:
+
The {{ic|nofail}} option is best combined with the {{ic|x-systemd.device-timeout}} option. This is because the default device timeout is 90 seconds, so a disconnected external device with only {{ic|nofail}} will make your boot take 90 seconds longer, unless you reconfigure the timeout as shown. Make sure not to set the timeout to 0, as this translates to infinite timeout.
{{hc|/etc/fstab|tmpfs /tmp      tmpfs nodev,nosuid                  0 0}}
+
  
You may or may not want to specify the size here, but you should leave the {{ic|mode}} option alone in these cases to ensure that they have the correct permissions (1777). In the example above, {{ic|/tmp}} will be set to use up to half of your total RAM. To explicitly set a maximum size, use the {{ic|size}} mount option:
+
If your external device requires another systemd unit to be loaded (for example the network for a network share) you can use {{ic|1=x-systemd.requires=x}} combined with {{ic|x-systemd.automount}}to postpone automounting until after the unit is available. For example:
{{hc|/etc/fstab|2=tmpfs /tmp      tmpfs nodev,nosuid,size=2G          0 0}}
+
  
Here is a more advanced example showing how to add tmpfs mounts for users.  This is useful for websites, mysql tmp files, {{ic|~/.vim/}}, and more.  It's important to try and get the ideal mount options for what you are trying to accomplish.  The goal is to have as secure settings as possible to prevent abuse.  Limiting the size, and specifying uid and gid + mode is very secure.  [[#Other_resources|More info]].
+
{{hc|/etc/fstab|2=
{{hc|/etc/fstab|2=tmpfs /www/cache tmpfs rw,size=1G,nr_inodes=5k,noexec,nodev,nosuid,uid=648,gid=648,mode=1700 0 0}}
+
//host/share        /net/share        cifs        noauto,nofail,x-systemd.automount,x-systemd.requires=network-online.target,x-systemd.device-timeout=10,workgroup=workgroup,credentials=/foo/credentials        0 0}}
  
See the '''mount''' command man page for more information. One useful mount option in the man page is the '''default''' option, understand that at least.
+
=== Filepath spaces ===
  
Reboot for the changes to take effect. Note that although it may be tempting to simply run {{ic|mount -a}} to make the changes effective immediately, this will make any files currently residing in these directories inaccessible (this is especially problematic for running programs with lockfiles, for example). However, if all of them are empty, it should be safe to run {{ic|mount -a}} instead of rebooting (or mount them individually).
+
Since spaces are used in {{ic|fstab}} to delimit fields, if any field (''PARTLABEL'', ''LABEL'' or the mount point) contains spaces, these spaces must be replaced by escape characters {{ic|\}} followed by the 3 digit octal code {{ic|040}}:
  
After applying changes, you may want to verify that they took effect by looking at {{ic|/proc/mounts}} and using {{ic|findmnt}}:
+
{{hc|/etc/fstab|2=
{{hc|<nowiki>$ findmnt --target /tmp</nowiki>|<nowiki>TARGET SOURCE FSTYPE OPTIONS
+
UUID=47FA-4071    /home/username/Camera<font color="grey">\040</font>Pictures   vfat defaults,noatime      0  0
/tmp   tmpfs tmpfs  rw,nosuid,nodev,relatime</nowiki>}}
+
/dev/sda7          /media/100<font color="grey">\040</font>GB<font color="grey">\040</font>(Storage)      ext4  defaults,noatime,user  0  2
 +
}}
  
To use tmpfs for {{ic|/var/lock}} and {{ic|/var/run}}, you can simply symlink them to {{ic|/run}}, or even better, bind mount them. Make sure to close anything important before doing this, because you will have to reboot, and daemons may not stop cleanly.
+
=== atime options ===
  
{{bc|<nowiki># ln -sf /run/lock /var/lock
+
Below atime options can impact drive performance.
# ln -sf /run /var/run
+
# reboot</nowiki>}}
+
  
{{Note|Arch does the symlinking as of {{pkg|initscripts}} 2011.12.1-1. See {{bug|18157}}.}}
+
* The {{ic|strictatime}} option updates the ''atime'' of the files every time they are accessed. This is more purposeful when Linux is used for servers; it does not have much value for desktop use. The drawback about the {{ic|strictatime}} option is that even reading a file from the page cache (reading from memory instead of the drive) will still result in a write!
{{Warning|Some daemons still have files and/or directories installed into {{ic|/var/lock}} and {{ic|/var/run}}, and the {{ic|/etc/rc.d/}} scripts may need to be edited for them to work.}}
+
 
 +
* The {{ic|noatime}} option fully disables writing file access times to the drive every time you read a file. This works well for almost all applications, except for a rare few like [[Mutt]] that needs such information. For mutt, you should only use the {{ic|relatime}} option. The write time information to a file will continue to be updated anytime the file is written to with this option enabled.
 +
 
 +
* The {{ic|nodiratime}} option disables the writing of file access times only for directories while other files still get access times written.
 +
: {{Note|{{ic|noatime}} already includes {{ic|nodiratime}}. [http://lwn.net/Articles/244941/ You do not need to specify both].}}
 +
 
 +
* {{ic|relatime}} enables the writing of file access times only when the file is being modified (unlike {{ic|noatime}} where the file access time will never be changed and will be older than the modification time). The best compromise might be the use this option since programs like [[Mutt]] will continue to work, but you will still have a performance boost as the files will not get access times updated unless they are modified. This option is used when the {{ic|defaults}} keyword option, {{ic|atime}} option (which means to use the kernel default, which is relatime; see {{ic|man 8 mount}} and [[wikipedia:Stat (system call)#Solutions]]) or no options at all are specified in ''fstab'' for a given mount point.
 +
 
 +
The {{ic|noatime}} and {{ic|relatime}} options avoid writes to the file system when files are read but not modified, which results in better performance.
  
 
=== Writing to FAT32 as Normal User ===
 
=== Writing to FAT32 as Normal User ===
To write on a fat32 partition you have to ake a few changes to your '/etc/fstab' file.
 
/dev/hdX /mnt/Y vfat user,rw,umask=000 0 0
 
  
The 'user' flag means that any user (even non-root) can mount and unmount the partition '/dev/hdX'. 'rw' gives read-write access, 'umask' option remove selected rights - for example 'umask=111' remove executable rights. The problem is, that this entry remove executable rights from directories too, so we must correct it by 'dmask=000'.
+
To write on a FAT32 partition, you must make a few changes to your {{ic|/etc/fstab}} file.
And why using this options? Without thats all files will be executable. You can use instead of umask and dmask option 'showexec', which shows all windows executables (com,exe,bat) in executable colours.
+
 
 +
{{hc|/etc/fstab|2=
 +
/dev/sdxY    /mnt/some_folder  vfat  '''user''',rw,umask=000              0  0}}
 +
 
 +
The {{ic|user}} flag means that any user (even non-root) can mount and unmount the partition {{ic|/dev/sdX}}. {{ic|rw}} gives read-write access;
 +
{{ic|umask}} option removes selected rights - for example {{ic|1=umask=111}} remove executable rights. The problem is that this entry removes executable rights from directories too, so we must correct it by {{ic|1=dmask=000}}. See also [[Umask]].
 +
 
 +
Without these options, all files will be executable. You can use the option {{ic|showexec}} instead of the umask and dmask options, which shows all Windows executables (com, exe, bat) in executable colours.
 +
 
 +
For example, if your FAT32 partition is on {{ic|/dev/sda9}}, and you wish to mount it to {{ic|/mnt/fat32}}, then you would use:
 +
 
 +
{{hc|/etc/fstab|2=
 +
/dev/sda9    /mnt/fat32        vfat  '''user''',rw,umask=111,dmask=000    0  0}}
 +
 
 +
Now, any user can mount it with:
 +
 
 +
$ mount /mnt/fat32
 +
 
 +
And unmount it with:
 +
 
 +
$ umount /mnt/fat32
 +
 
 +
=== Remounting the root partition ===
 +
 
 +
If for some reason the root partition has been improperly mounted read only, remount the root partition with read-write access with the following command:
 +
 
 +
# mount -o remount,rw /
 +
 
 +
=== bind mounts ===
 +
 
 +
{{Expansion|unfinished section}}
 +
 
 +
{{Note|Binding a directory to a different location is not recognised by almost any program, so for instance careless commands like {{ic|rm -r *}} will also erase any content from the original location. So softlinks should be the preferable way in most cases. If you need permission to a directory on a Btrfs and softlinks are not sufficient its [[Btrfs#Subvolumes|subvolumes]] faciliate extended capabilities like mount options compared to bind mounting}}
  
For example, if your fat32 partition is on '/dev/hda9' and you wish to mount it to '/mnt/fat32' then you would type in
+
Sometimes programs or users cannot access one specific directory due to insufficient permissions. One feasable possibility to give the program access to this directory is bind mounting it to a location the program can access. If a program has permission to access directory bar but not to directory foo, under some circumstances the access can be granted without any permission hassle by adding an entry to {{ic|/etc/fstab}}:
/dev/hda9 /mnt/fat32 vfat user,rw,umask=111,dmask=000 0 0
+
{{hc|/etc/fstab|2=
 +
/<path to foo>        /<path to bar>    none    bind    0 0}}
  
==Related==
+
== See also ==
* [[Persistent block device naming]]
+
* [[NTFS Write Support]]
+
* [[Firefox Ramdisk]]
+
* [[Using tmpfs for /var/*]]
+
* [[Boot Debugging]]
+
  
==See also==
+
* [http://www.kernel.org/pub/linux/docs/lanana/device-list/devices-2.6.txt Full device listing including block device]
*[[Wikipedia:Fstab]]
+
* [http://www.pathname.com/fhs/2.2/index.html Filesystem Hierarchy Standard]
*[http://www.tuxfiles.org/linuxhelp/fstab.html tuxfiles]
+
* [http://www.askapache.com/web-hosting/super-speed-secrets.html 30x Faster Web-Site Speed] (Detailed tmpfs)
*[http://www.kernel.org/pub/linux/docs/device-list/devices.txt Full device listing including block device]
+
* [[Samba#Add Share to /etc/fstab|Adding Samba shares to /etc/fstab]]
*[http://www.pathname.com/fhs/2.2/index.html Filesystem Hierarchy Standard]
+
*[http://www.askapache.com/web-hosting/super-speed-secrets.html 30x Faster Web-Site Speed] (Detailed tmpfs)
+

Latest revision as of 00:00, 23 May 2016

The /etc/fstab file can be 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, and when the configuration of the system manager is reloaded. 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 mount command will use fstab, if just one of either directory or device is given, to fill in the value for the other parameter. When doing so, mount options which are listed in fstab will also be used.

File example

A simple /etc/fstab, using kernel name descriptors:

/etc/fstab
# <file system>        <dir>         <type>    <options>             <dump> <pass>
/dev/sda1              /             ext4      defaults,noatime      0      1
/dev/sda2              none          swap      defaults              0      0
/dev/sda3              /home         ext4      defaults,noatime      0      2

Field definitions

Each line in the /etc/fstab file contains the following fields separated by spaces or tabs:

file_system    dir    type    options    dump    pass
file system
The partition or storage device to be mounted.
dir
The mountpoint where <file system> is mounted to.
type
The file system type of the partition or storage device to be mounted. Many different file systems are supported: ext2, ext3, ext4, btrfs, reiserfs, xfs, jfs, smbfs, iso9660, vfat, ntfs, swap and auto. The auto type lets the mount command guess what type of file system is used. This is useful for optical media (CD/DVD).
options
Mount options of the filesystem to be used. See the mount man page. Please note that some options are specific to filesystems; to discover them see below in the aforementioned mount man page.
dump
Used by the dump utility to decide when to make a backup. Dump checks the entry and uses the number to decide if a file system should be backed up. Possible entries are 0 and 1. If 0, dump will ignore the file system; if 1, dump will make a backup. Most users will not have dump installed, so they should put 0 for the dump entry.
pass
Used by fsck to decide which order filesystems are to be checked. Possible entries are 0, 1 and 2. The root file system should have the highest priority 1 (unless its type is btrfs, in which case this field should be 0) - all other file systems you want to have checked should have a 2. File systems with a value 0 will not be checked by the fsck utility.

Identifying filesystems

There are different ways to identify filesystems that will be mounted. /etc/fstab does support several methods: kernel name descriptor, label or UUID, and GPT labels and UUID for GPT disks. UUID must be privileged over kernel name descriptors and labels. See Persistent block device naming for more explanations. It is recommended to read that article first before continuing with this article.

In this section, we will describe how to mount filesystems using all the mount methods available via examples. The output of the commands lsblk -f and blkid used in the following examples are available in the article Persistent block device naming. If you have not read that article yet, please read it now.

Kernel name descriptors

Run lsblk -f to list the partitions and prefix the values in the NAME column with /dev/.

/etc/fstab
# <file system> <dir> <type> <options>                                                                                            <dump> <pass>
/dev/sda1       /boot vfat   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0      2
/dev/sda2       /     ext4   rw,relatime,discard,data=ordered                                                                     0      1
/dev/sda3       /home ext4   rw,relatime,discard,data=ordered                                                                     0      2
/dev/sda4       none  swap   defaults                                                                                             0      0

Labels

Run lsblk -f to list the partitions, and prefix the values in the LABEL column with LABEL=:

/etc/fstab
# <file system> <dir> <type> <options>                                                                                            <dump> <pass>
LABEL=EFI       /boot vfat   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0      2
LABEL=SYSTEM    /     ext4   rw,relatime,discard,data=ordered                                                                     0      1
LABEL=DATA      /home ext4   rw,relatime,discard,data=ordered                                                                     0      2
LABEL=SWAP      none  swap   defaults                                                                                             0      0
Note: If any of your fields contains spaces, see #Filepath spaces.

UUIDs

Run lsblk -f to list the partitions, and prefix the values in the UUID column with UUID=:

/etc/fstab
# <file system>                           <dir> <type> <options>                                                                                            <dump> <pass>
UUID=CBB6-24F2                            /boot vfat   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0      2
UUID=0a3407de-014b-458b-b5c1-848e92a327a3 /     ext4   rw,relatime,discard,data=ordered                                                                     0      1
UUID=b411dc99-f0a0-4c87-9e05-184977be8539 /home ext4   rw,relatime,discard,data=ordered                                                                     0      2
UUID=f9fe0b69-a280-415d-a03a-a32752370dee none  swap   defaults                                                                                             0      0
Tip: If you would like to return just the UUID of a specific partition: $ lsblk -no UUID /dev/sda2

GPT labels

Run blkid to list the partitions, and use the PARTLABEL values without the quotes:

/etc/fstab
# <file system>                      <dir> <type> <options>                                                                                            <dump> <pass>
PARTLABEL=EFI\040SYSTEM\040PARTITION /boot vfat   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0      2
PARTLABEL=GNU/LINUX                  /     ext4   rw,relatime,discard,data=ordered                                                                     0      1
PARTLABEL=HOME                       /home ext4   rw,relatime,discard,data=ordered                                                                     0      2
PARTLABEL=SWAP                       none  swap   defaults                                                                                             0      0
Note: If any of your fields contains spaces, see #Filepath spaces.

GPT UUIDs

Run blkid to list the partitions, and use the PARTUUID values without the quotes:

/etc/fstab
# <file system>                               <dir> <type> <options>                                                                                            <dump> <pass>
PARTUUID=d0d0d110-0a71-4ed6-936a-304969ea36af /boot vfat   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0      2
PARTUUID=98a81274-10f7-40db-872a-03df048df366 /     ext4   rw,relatime,discard,data=ordered                                                                     0      1
PARTUUID=7280201c-fc5d-40f2-a9b2-466611d3d49e /home ext4   rw,relatime,discard,data=ordered                                                                     0      2
PARTUUID=039b6c1c-7553-4455-9537-1befbc9fbc5b none  swap   defaults                                                                                             0      0

Tips and tricks

Automount with systemd

If you have a large /home partition, it might be better to allow services that do not depend on /home to start while /home is checked by fsck. This can be achieved by adding the following options to the /etc/fstab entry of your /home partition:

noauto,x-systemd.automount

This will fsck and mount /home when it is first accessed, and the kernel will buffer all file access to /home until it is ready.

Note: This will make your /home filesystem type autofs, which is ignored by mlocate by default. The speedup of automounting /home may not be more than a second or two, depending on your system, so this trick may not be worth it.

The same applies to remote filesystem mounts. If you want them to be mounted only upon access, you will need to use the noauto,x-systemd.automount parameters. In addition, you can use the x-systemd.device-timeout=# option to specify a timeout in case the network resource is not available.

Note: If you intend to use the exec flag with automount, you should remove the user flag for it to work properly as found in the course of a Fedora Bug Report

If you have encrypted filesystems with keyfiles, you can also add the noauto parameter to the corresponding entries in /etc/crypttab. systemd will then not open the encrypted device on boot, but instead wait until it is actually accessed and then automatically open it with the specified keyfile before mounting it. This might save a few seconds on boot if you are using an encrypted RAID device for example, because systemd does not have to wait for the device to become available. For example:

/etc/crypttab
data /dev/md0 /root/key noauto

You may also specify an idle timeout for a mount with the x-systemd.idle-timeout flag. For example:

noauto,x-systemd.automount,x-systemd.idle-timeout=1min

This will make systemd unmount the mount after it has been idle for 1 minute.

External devices

External devices that are to be mounted when present but ignored if absent may require the nofail option. This prevents errors being reported at boot. For example:

/etc/fstab
/dev/sdg1        /media/backup    jfs    defaults,nofail,x-systemd.device-timeout=1    0  2

The nofail option is best combined with the x-systemd.device-timeout option. This is because the default device timeout is 90 seconds, so a disconnected external device with only nofail will make your boot take 90 seconds longer, unless you reconfigure the timeout as shown. Make sure not to set the timeout to 0, as this translates to infinite timeout.

If your external device requires another systemd unit to be loaded (for example the network for a network share) you can use x-systemd.requires=x combined with x-systemd.automountto postpone automounting until after the unit is available. For example:

/etc/fstab
//host/share        /net/share        cifs        noauto,nofail,x-systemd.automount,x-systemd.requires=network-online.target,x-systemd.device-timeout=10,workgroup=workgroup,credentials=/foo/credentials        0 0

Filepath spaces

Since spaces are used in fstab to delimit fields, if any field (PARTLABEL, LABEL or the mount point) contains spaces, these spaces must be replaced by escape characters \ followed by the 3 digit octal code 040:

/etc/fstab
UUID=47FA-4071     /home/username/Camera\040Pictures   vfat  defaults,noatime       0  0
/dev/sda7          /media/100\040GB\040(Storage)       ext4  defaults,noatime,user  0  2

atime options

Below atime options can impact drive performance.

  • The strictatime option updates the atime of the files every time they are accessed. This is more purposeful when Linux is used for servers; it does not have much value for desktop use. The drawback about the strictatime option is that even reading a file from the page cache (reading from memory instead of the drive) will still result in a write!
  • The noatime option fully disables writing file access times to the drive every time you read a file. This works well for almost all applications, except for a rare few like Mutt that needs such information. For mutt, you should only use the relatime option. The write time information to a file will continue to be updated anytime the file is written to with this option enabled.
  • The nodiratime option disables the writing of file access times only for directories while other files still get access times written.
Note: noatime already includes nodiratime. You do not need to specify both.
  • relatime enables the writing of file access times only when the file is being modified (unlike noatime where the file access time will never be changed and will be older than the modification time). The best compromise might be the use this option since programs like Mutt will continue to work, but you will still have a performance boost as the files will not get access times updated unless they are modified. This option is used when the defaults keyword option, atime option (which means to use the kernel default, which is relatime; see man 8 mount and wikipedia:Stat (system call)#Solutions) or no options at all are specified in fstab for a given mount point.

The noatime and relatime options avoid writes to the file system when files are read but not modified, which results in better performance.

Writing to FAT32 as Normal User

To write on a FAT32 partition, you must make a few changes to your /etc/fstab file.

/etc/fstab
/dev/sdxY    /mnt/some_folder  vfat   user,rw,umask=000              0  0

The user flag means that any user (even non-root) can mount and unmount the partition /dev/sdX. rw gives read-write access; umask option removes selected rights - for example umask=111 remove executable rights. The problem is that this entry removes executable rights from directories too, so we must correct it by dmask=000. See also Umask.

Without these options, all files will be executable. You can use the option showexec instead of the umask and dmask options, which shows all Windows executables (com, exe, bat) in executable colours.

For example, if your FAT32 partition is on /dev/sda9, and you wish to mount it to /mnt/fat32, then you would use:

/etc/fstab
/dev/sda9    /mnt/fat32        vfat   user,rw,umask=111,dmask=000    0  0

Now, any user can mount it with:

$ mount /mnt/fat32

And unmount it with:

$ umount /mnt/fat32

Remounting the root partition

If for some reason the root partition has been improperly mounted read only, remount the root partition with read-write access with the following command:

# mount -o remount,rw /

bind mounts

Tango-view-fullscreen.pngThis article or section needs expansion.Tango-view-fullscreen.png

Reason: unfinished section (Discuss in Talk:Fstab#)
Note: Binding a directory to a different location is not recognised by almost any program, so for instance careless commands like rm -r * will also erase any content from the original location. So softlinks should be the preferable way in most cases. If you need permission to a directory on a Btrfs and softlinks are not sufficient its subvolumes faciliate extended capabilities like mount options compared to bind mounting

Sometimes programs or users cannot access one specific directory due to insufficient permissions. One feasable possibility to give the program access to this directory is bind mounting it to a location the program can access. If a program has permission to access directory bar but not to directory foo, under some circumstances the access can be granted without any permission hassle by adding an entry to /etc/fstab:

/etc/fstab
/<path to foo>         /<path to bar>     none     bind     0 0

See also