471
you are viewing a single comment's thread
view the rest of the comments
[-] UntouchedWagons@lemmy.ca 37 points 1 year ago* (last edited 1 year ago)

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.target
[-] Technoguyfication@lemmy.ml 15 points 1 year ago* (last edited 1 year ago)

I’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)

[-] Still@programming.dev 7 points 1 year ago

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

[-] UntouchedWagons@lemmy.ca 5 points 1 year ago

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.

[-] exu@feditown.com 2 points 1 year ago

Systemd can retry mounting based on the restart policy in case you have an interruption.

[-] hemko@lemmy.dbzer0.com 6 points 1 year ago

Kinda interested now, why would you use systemd script for this instead of fstab ?

[-] UntouchedWagons@lemmy.ca 2 points 1 year ago

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.

[-] hemko@lemmy.dbzer0.com 2 points 1 year ago

Oh that's actually really good reason with docker containers that rely on the NFS share. Thanks, I'm gonna steal this

[-] elscallr@lemmy.world 2 points 1 year ago

So you can easily start and stop it as a service and you get your logging easily accessible via journalctl as a unit. But practically speaking there's not much difference.

[-] ninekeysdown@lemmy.world 6 points 1 year ago

Yeap! You can even make an automount unit too! That way it’s mounted on demand! Makes life sooo much easier. I even do it for my external drives I use for backups

[-] Sanjoooo@feddit.de 3 points 1 year ago

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.

[-] 5redie8@sh.itjust.works 3 points 1 year ago

How would you do this with fstab? (Working with an smb share which I'm assuming is standard)

[-] Sanjoooo@feddit.de 1 points 1 year ago
[-] sudo@lemmy.today 3 points 1 year ago

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.

[-] Sanjoooo@feddit.de 3 points 1 year ago

That sounds useful, thank you very much.

[-] JoCrichton@lemmy.world 3 points 1 year ago

An now explain how to setup Kerberos

[-] andrew@lemmy.stuart.fun 1 points 1 year ago
What=Kerberos
Where=pam
[-] UntouchedWagons@lemmy.ca 1 points 1 year ago

No idea, I don't use Kerberos.

[-] Eccitaze@yiffit.net 0 points 1 year ago

Oh that's easy! I have this friendly multi-page PDF that assumes you have an active directory domain already (god rest your soul if you're raw dogging kerberos and ldap raw) that walks you through the instructions step by step and...

mount.nfs4: access denied by server

this post was submitted on 06 Aug 2023
471 points (97.0% liked)

linuxmemes

21251 readers
1598 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS