You are not logged in.
I have the following line in /etc/fstab:
192.168.1.5:/srv/nsf4/main /shares nfs noauto,nofail,x-systemd.automount,_netdev,x-systemd.device-timeout=14,size=32768,wsize=32768 0 0This works properly in the sense that systemd does not hold up the system when booting, and it does mount the directory upon first access, however the system hangs at shutdown in a manner consistent with systemd shutting down the network before attempting to unmount the drive. Indeed, even when the system is running, I can manually run
systemctl stop NetworkManager.serviceand a call to
systemctl status shares.mountshows that the mount is still active.
I can't attach anything, but here's a pastebin of my shutdown log:
http://pastebin.com/rTJxZDF5
Also, here's what I get from systemctl show shares.mount:
http://pastebin.com/a9ZUeX6z
Finally, I will describe the debugging I have done to this point. First, if I manually unmount the share before shutting down, it shuts down immediately. I am using systemd's automount option, however the same thing happens without automount (or fstab for that matter - simply manually mounting an NFS share and shutting down results in the shutdown taking about 2-3 minutes). I also added additional items to the Require= and After= lines for shares.mount, specifically I tried adding network.target, NetworkManager.service, and wpa_supplicant.service. In each case, I did observe that manually running
systemctl stop NetworkManager.service(for instance) now did cause the share to be unmounted, however if I shutdown the computer without manually stopping NetworkManager.service, for instance, it would still stall for 2 minutes before timing out.
Last edited by process91 (2015-04-02 02:20:37)
Offline
This seems to be an upstream bug, the problem is that DBus stops too soon. Here's a link to the bug report:
https://bugs.launchpad.net/ubuntu/+sour … ug/1438612
Offline
I have the same problem, I tried the solutions:
* adding After=dbus.service to /lib/systemd/system/NetworkManager.service's [Unit] section
* adding ExecStop=/bin/true and KillMode=none to /lib/systemd/system/dbus.service [Service] section
Both didn't work. How did you fix this?
Offline
I have had similar problems, although on my system, I use fstab to mount the NAS to /mnt and then I use bind mounts to mount NAS folders to my home directory.
Without the bind mounts everything worked perfectly. WIth the bind mounts, the system would hang on shutdown/reboot.
Unfortunately, I only experience this problem with NetworkManager. I use Gnome, so would love the network integration, but this issue is a deal breaker for me. Currently I use systemd-networkd with a custom extension to show network connectivity in the Gnome panel. The shutdown process works flawlessly (bind mounts and NAS mounts both mounted and unmounted without issue).
Obviously not an ideal solution, but perhaps try using something other then NetworkManager to see if you still experience issues, if not, it does isolate the issue to being a NetworkManager problem.
I do want to go back to NetworkManager for the integration with my desktop aspect, but for now I am happy with a working system without it.
Cheers.
Offline