Bug#835810: systemd nfs mount timeout leaves mount unit in active state, preventing later automounts
biebl at debian.org
Sun Aug 28 16:51:00 BST 2016
Am 28.08.2016 um 17:24 schrieb Tero Marttila:
> The fstab entry for this specific mount:
>> nfs.test.pvl:mail /srv/mail nfs4
>> defaults,auto,nodev,nosuid,noatime,x-systemd.automount 0 0
I think you really want "noauto" instead of "auto" here, so the share is
only mounted on demand.
That said, it looks like your network setup does not properly hook up
the network-online.target, so the nfs mounts are attempted before the
network is actually up.
Could you share details about your network configuration like
It is odd though indeed, that systemd marks your nfs share as mounted
when it actually isn't. It seems I can reproduce that issue with v231 as
well. I've created a test share on a server, stopped the network and
then tried to mount the nfs share via
systemctl start mnt-nfs.mount. The result is the same:
● mnt-nfs.mount - /mnt/nfs
Loaded: loaded (/etc/fstab; generated; vendor preset: enabled)
Active: active (mounted) (Result: timeout) since So 2016-08-28
17:48:53 CEST; 27s ago
Process: 9538 ExecMount=/bin/mount 192.168.179.10:/srv/nfs /mnt/nfs -t
nfs4 (code=killed, signal=TERM)
Tasks: 0 (limit: 4915)
Aug 28 17:47:23 pluto systemd: Mounting /mnt/nfs...
Aug 28 17:48:53 pluto systemd: mnt-nfs.mount: Mounting timed out.
Aug 28 17:48:53 pluto systemd: Mounted /mnt/nfs.
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 801 bytes
Desc: OpenPGP digital signature
More information about the Pkg-systemd-maintainers