NFS unmount (over wireless network) causing shutdown delay

General system Newbie
21

I’ve noticed a thing, I see/read what I expect :slight_smile: And my morning eyes are especially faulty.
I’ll test it for different behavior.

22

And, give that @Moonbase59 guy a sucker for passing his eye exams.
And the original post that @SemLraug referenced.
Shutdown went to almost instant (and I can blame the almost part on a VPN kernel module which takes 4 seconds).
I’m going to flag the OP as the solution, though MY solution was someone noticing my typo. Thanks guys, and I really didn’t mean to give any of us a free eye exam.

I’m so used to fstab not tolerating typos that I didn’t expect one to pass muster.

1 Like
23

Glad we got it solved together!

1 Like
24

We live in expensive times, so anything free is welcome.

Great that things got sorted.

25

Hah, and when I turned it on this night, it didn’t mount the drive lol during bootup, though mount -a worked. I changed a couple params and will go back to bed, and see what tomorrow brings for the mount.
The gift that keeps on giving ;0

26

That’s a plot twist i did not expect. :roll_eyes:

27

And yep, the morning trial is that not only did it not mount, but there’s nothing referencing the mount point nor the hostname/ip in the journal. As if it was totally commented out.

Added: I got it! I converted to an automount volume to mount on the first usage. After some experimentation (still not 100% successful), it works, and still shutdowns down gracefully. However, the ‘auto’ mounting, doesn’t work…but as long as it mounts it when needed, I’m good.

pharazon:/raid          /mnt/raid                       nfs     _netdev,auto,x-systemd.automount,x-systemd.mount-timeout=10,timeo=14,x-systemd.idle-timeout=1min,x-systemd.requires=network-online.target 0 0

Added 2: How can such a simple little thing be so tricky?

28

Yes it (unfortunately) is tricky.

Try

pharazon:/raid /mnt/raid nfs users,noauto,nofail,async,noatime,_netdev,x-systemd.automount,x-systemd.device-timeout=10s,x-systemd.mount-timeout=10s,retry=1,x-systemd.idle-timeout=1min 0 0

Hints:

  • noauto is required for “on-demand” mounting (so it doesn’t automount on boot (as root))
  • user or users is needed so it can be mounted/unmounted as non-root user
  • nofail is needed so it doesn’t complain and wait endlessly while booting (and if not reachable)
  • retry=1 is needed so you don’t have to wait shy of 7 days for retries (its default is 10000 minutes)
  • _netdev implies x-systemd.requires=network-online.target
  • async allows mem caching and is faster; for immediate syncing use sync instead (safer but slower)

For the behaviour of this suggestion, read Automount NFS share on access, again.

29

Actually I wanted it to automount on boot :wink: But that was the part that didn’t work.
However, even w/o users, it’s mounting on access as is for me, so everything is satisfactorily working.
I may add some of your options for good measure and retest.

1 Like
30

Good luck! Mine is from my laptop, which isn’t always in the home network, so I opted for “on-access mount”.

31

Yep, my desktop has never left my local area network (yet) :slight_smile:

1 Like
32

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.