The basic and introductory information about systemd can be found on the manual page systemd-start. The sections [Unit] and [Install] concerning all unit files are covered on our manual page systemd unit file.
On this manual page we explain the function of the systemd units mount and automount. They are used by systemd to manage mount points for drives and their partitions, which can be accessible both locally and over the network.
The mount unit is a configuration file that provides systemd with information about a mount point.
The automount unit monitors the file system and activates the .mount unit of the same name if the file system designated therein is available.
For drives and their partitions directly installed in the PC we only use the mount unit. It is enabled and started to mount the drives at each boot.
For network file systems, the mount unit has the advantage of being able to declare dependencies so that the unit only becomes active when the network is ready. Again, we use only the mount unit and activate and start it to mount the network file system at each boot. The mount unit supports all types of network file systems (NFS, SMB, FTP, WEBDAV, SFTP, SSH).
Removable devices, such as USB sticks and network file systems that are not permanently accessible, must always be attached to a .automount unit. In this case, the mount unit must not be activated and should not contain an [Install] section.
mount and automount units must be named after the mount point they control. For example, the mount point “/home/exampleuser” must be configured in a unit file “home-musteruser.mount”, or “home-musteruser.automount”.
The devices declared in /etc/fstab and their mount points are translated into native mount units by systemd in the early boot phase using the systemd-fstab-generator.
The mount unit has the following options in the mandatory [Mount] section:
What= (mandatory)
contains the absolute path of the mounted device, e.g., disk partitions such as /dev/sda8 or a network share such as NFSv4 or Samba.
Where= (mandatory)
Here you specify the mount point, i.e. the folder where the partition, network drive, or device should be mounted. If it does not exist, it will be created during the mount process.
Type= (optional)
Here the type of the file system is specified, according to the mount parameter -t.
Options= (optional)
contains all used options in a comma separated list, according to the mount parameter -o.
LazyUmount= (default: off)
If set to true, the filesystem will be unmounted as soon as it is no longer needed.
SloppyOptions= (default: off)
If true, a relaxed evaluation of the options specified in Options= is performed and unknown mount options are tolerated. This is equivalent to the mount parameter -s.
ReadWriteOnly= (default: off)
If false, the file system or device that should be mounted read-write, but could not be mounted successfully, is attempted to be mounted read-only. If true, the process immediately ends with an error if the read-write mount fails. This is equivalent to the -w mount parameter.
ForceUnmount= (default: off).
If true, unmounting is forced if, for example, an NFS file system is unreachable. This corresponds to the mount parameter -f.
DirectoryMode= (default: 0755)
The, if necessary, automatically created directories of mount points get the declared file system access mode. Accepts an access mode in octal notation.
TimeoutSec= (default value from the DefaultTimeoutStartSec= option in systemd-system.conf).
Configures the time to wait for the mount command to finish. If a command does not finish within the configured time, the mount is considered to have failed and is shut down again. Accepts a unit-free value in seconds or a duration value such as “5min 20s”. Passing “0” will disable the timeout logic.
The automount unit has the following options in the mandatory [Automount] section:
Where= (mandatory)
This specifies the mount point, i.e. the folder where the partition, network drive, or device is to be mounted. If it does not exist, it will be created during the mount process.
DirectoryMode= (default: 0755)
The, if necessary, automatically created directories of mount points get the declared file system access mode. Accepts an access mode in octal notation.
TimeoutIdleSec= (default: 0)
specifies the time of inactivity after which systemd attempts to unmount the file system. Accepts a unitless value in seconds or a duration value such as “5min 20s”. The value “0” disables the option.
Systemd reads the mount point from the name of the mount and automount units. Therefore, they must be named after the mount point they control.
Make sure not to use hyphens “-” in the filenames, because they declare a new subdirectory in the directory tree. Some examples:
To get an error-free file name for the mount and automount units, we use the systemd-escape command in the terminal.
$ systemd-escape -p --suffix=mount "/data/home-backup"
data/home\x2dbackup.mountDisk partition
A partition should be accessible under /disks/TEST after every system start.
We create with a text editor the file “disks-TEST.mount” in the directory /usr/local/lib/systemd/system/. (If necessary, create the directory beforehand with the command mkdir -p /usr/local/lib/systemd/system/.)
[Unit]
Description=Mount /dev/sdb7 at /disks/TEST
After=blockdev@dev-disk-by\x2duuid-a7af4b19\x2df29d\x2d43bc\x2d3b12\x2d87924fc3d8c7.target
Requires=local-fs.target
Wants=multi-user.target
[Mount]
Where=/disks/TEST
What=/dev/disk/by-uuid/a7af4b19-f29d-43bc-3b12-87924fc3d8c7
Type=ext4
Options=defaults,noatime
[Install]
WantedBy=multi-user.targetThen we activate and start the new mount unit.
# systemctl enable --now disks-TEST.mountNFS
The “document-root” directory of an Apache web server in the home network is to be mounted into the home directory of the workstation computer using NFS.
We create the file home-<user>-www_data.mount in the /usr/local/lib/systemd/system/ directory using a text editor.
Please replace “<user>” with your own name.
[Unit]
Description=Mount server1/var/www/ using NFS
After=network-online.target
Wants=network-online.target
[Mount]
What=192.168.3.1:/
Where=/home/<user>/www_data
Type=nfs
Options=nfsvers=4,rw,users,soft
ForceUnmount=trueThis file does not contain an [Install] section and will not be activated. The control is taken over by the now following file home-<user>-www_data.automount in the same directory.
[Unit]
Description=Automount server1/var/www/ using NFS
ConditionPathExists=/home/<user>/www_data
Requires=NetworkManager.service
After=network-online.target
Wants=network-online.target
[Automount]
Where=/home/<user>/www_data
TimeoutIdleSec=60
[Install]
WantedBy=remote-fs.target
WantedBy=multi-user.targetAfterwards:
# systemctl enable --now home-<user>-www_data.automountNow the “document-root” directory of the Apache web server will be mounted as soon as we switch to the /home/<user>/www_data directory.
The status prompt confirms the action.
# systemctl status home-<user>-www_data.mount
home-<user>-www_data.mount Mount server1/var/www/ using NFS
Loaded: loaded (/usr/local/lib/systemd/system/home-<user>-www_data.mount; disabled; vendor preset: enabled)
Active: active (mounted) since Wed 2021-03-10 [...]
TriggeredBy: ● home-<user>-www_data.automount
Where: /home/<user>/www_data
What: 192.168.3.1:/
Tasks: 0 (limit: 4279)
Memory: 120.0K
CPU: 5ms
CGroup: /system.slice/home-<user>-www_data.mount
[...]
# systemctl status home-<user>-www_data.automount
home-<user>-www_data.automount Automount server1/var/www/ usuing NFS
Loaded: loaded (/usr/local/lib/systemd/system/home-<user>-www_data.automount; enabled; vendor preset: enabled)
Active: active (running) since Wed 2021-03-10 [...]
Triggers: ● home-<user>-www_data.mount
Where: /home/<user>/www_data
[...]The journal excerpt vividly logs the operation of “TimeoutIdleSec=60” to unmount the file system and mount it again by starting the file manager Thunar and a call to /home/<user>/www_data in the terminal.
# journalctl -f -u home-<user>-www_data.*
[...]systemd[1]: Mounted Mount server1/var/www/ using NFS
[...]systemd[1]: Unmounting Mount server1/var/www/ using NFS
[...]systemd[1]: home-<user>-www_data.mount: Succeeded.
[...]systemd[1]: Unmounted Mount server1/var/www/ using NFS
[...]systemd[1]: home-<user>-www_data.automount: Got
automount request for /home/<user>/www_data
triggered by 2500 (Thunar)
[...]systemd[1]: Mounting Mount server1/var/www/ using NFS
[...]systemd[1]: Mounted Mount server1/var/www/ using NFS
[...]systemd[1]: Unmounting Mount server1/var/www/ using NFS
[...]systemd[1]: home-<user>-www_data.mount: Succeeded.
[...]systemd[1]: Unmounted Mount server1/var/www/ using NFS
[...]systemd[1]: home-<user>-www_data.automount: Got
automount request for /home/<user>/www_data
triggered by 6582 (bash)
[...]systemd[1]: Mounting Mount server1/var/www/ using NFS
[...]systemd[1]: Mounted Mount server1/var/www/ using NFS
[...]systemd[1]: Unmounting Mount server1/var/www/ using NFS
[...]systemd[1]: home-<user>-www_data.mount: Succeeded.
[...]systemd[1]: Unmounted Mount server1/var/www/ using NFSMore examples
Using your favorite search engine, you can find many examples on how to use mount and automount units on the Internet. The chapter “Sources” contains some websites with lots of further examples. We urgently recommend to also read the man pages.
man systemd.mount
man mountManjaro Forum, systemd.mount
Manjaro Forum, Use systemd to mount ANY device