Arch Linux

freejack

Member

Registered: 2013-04-27

Posts: 6

[solved] systemd automount nfs broken since last full system update

I used systemd automount to mount my nfs server shares on demand on my wlan notebook. This worked quite well from April last year when I set up this machine until December 2013.

After a system upgrade the automount hangs (not just 90s, but forever). I replaced the systemd.automount entries with ordinary ones (see below). Mounting manually (e.g. with mount /server/home) works just fine, the mount is established instantly.

# this no longer works, blocks when mount is accessed
#raptor:/home		/server/home	nfs	intr,relatime,rw,vers=3,user,noauto,x-systemd.automount,nofail	 0 2

# works just fine, but needs manual mount
raptor:/home		/server/home	nfs	intr,relatime,rw,vers=3,user,noauto	 0 2

These are the related units (containing home and server or raptor) reported from systemctl --all:

server-home.automount                              loaded active   running   server-home.automount
raptor:-home.device                                loaded inactive dead      raptor:-home.device
server-home.mount                                  loaded inactive dead      /server/home
systemd-fsck@raptor:-home.service                  loaded inactive dead      File System Check on /raptor:/home

In journalctl and dmesg I cannot see anything related or suspicious. Any ideas how to track down or resolve this issue would be great.

Last edited by freejack (2014-01-11 11:29:50)

molwhe

Member

Registered: 2014-01-09

Posts: 1

Re: [solved] systemd automount nfs broken since last full system update

Change that pass number in your fstab entry to a 0 instead of a 2.  Systemd is expecting to fsck your nfs mount which is not possible, so it fails to mount.

raptor:/home		/server/home	nfs	intr,relatime,rw,vers=3,user,noauto,x-systemd.automount,nofail	 0 0

freejack

Member

Registered: 2013-04-27

Posts: 6

Re: [solved] systemd automount nfs broken since last full system update

Change that pass number in your fstab entry to a 0 instead of a 2...

Thanks, that solved it.