you can stop and start it via systemctl and systemd is going to make mounts for fstab entries automatically, I just put local drives in my fstab so that way I can copy mount files between machines
With these systemd mount files I don’t need to touch the fstab, I can use ansible to copy the file, enable the service then start it. I can also have other services like Docker, Jellyfin or whatever to depend on that service. If the nfs share can’t be mounted then systemd won’t try to start docker.
With these systemd mount files I don’t need to touch the fstab, I can use ansible to copy the file, enable the service then start it. I can also have other services like Docker, Jellyfin or whatever to depend on that service. If the nfs share can’t be mounted then systemd won’t try to start docker.
Linux user here, this would have been super helpful to me in the past. I don’t think it’s that the world is full of master Linux users that don’t post, it’s that new people need more help and have more questions.
I’ll probably switch to simple script, since I don’t like the idea of my laptop shouting my NAS access credentials into any available random network on startup.
You may want to consider adding nofail and x-systemd.device-timeout opinions on the mount as well if the NFS isn’t critical to the device booting, and speed up your boot process a bit.
Here’s how to mount an nfs share:
#cat /etc/systemd/system/mnt.data.mount [Unit] Description=nfs mount script [Mount] What=192.168.0.30:/mnt/tank/Media Where=/mnt/data Type=nfs4 [Install] WantedBy=remote-fs.targetI’ve always mounted network shares in fstab, what’s the benefit to doing it with systemd?
(Also, for those of you learning, this method only works on systemd-based distros)
you can stop and start it via systemctl and systemd is going to make mounts for fstab entries automatically, I just put local drives in my fstab so that way I can copy mount files between machines
With these systemd mount files I don’t need to touch the fstab, I can use ansible to copy the file, enable the service then start it. I can also have other services like Docker, Jellyfin or whatever to depend on that service. If the nfs share can’t be mounted then systemd won’t try to start docker.
Systemd can retry mounting based on the restart policy in case you have an interruption.
Kinda interested now, why would you use systemd script for this instead of fstab ?
With these systemd mount files I don’t need to touch the fstab, I can use ansible to copy the file, enable the service then start it. I can also have other services like Docker, Jellyfin or whatever to depend on that service. If the nfs share can’t be mounted then systemd won’t try to start docker.
Oh that’s actually really good reason with docker containers that rely on the NFS share. Thanks, I’m gonna steal this
deleted by creator
Linux user here, this would have been super helpful to me in the past. I don’t think it’s that the world is full of master Linux users that don’t post, it’s that new people need more help and have more questions.
Meanwhile I found a solution using fstab.
What’s the advantage of using a systemd script?
I’ll probably switch to simple script, since I don’t like the idea of my laptop shouting my NAS access credentials into any available random network on startup.
How would you do this with fstab? (Working with an smb share which I’m assuming is standard)
I described what I did here.
You may want to consider adding nofail and x-systemd.device-timeout opinions on the mount as well if the NFS isn’t critical to the device booting, and speed up your boot process a bit.