[systemd-bugs] [Bug 73727] remote file systems cannot be unmounted at shutdown

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Jan 17 08:05:44 PST 2014


https://bugs.freedesktop.org/show_bug.cgi?id=73727

--- Comment #6 from Mario Natiello <mario.natiello at gmail.com> ---
(In reply to comment #5)
> > We also can't fix this by adding After=network.target and After=NetworkManager.service to every mount.
> 
> To clarify, having re-read your comment, we also can't do this for
> systemd-user-sessions.service for the same reasons.

Addendum: The modification I proposed does not work either. Or it is at least
erratic. Not having changed other things, I twice found myself in the situation
where umount of the remote systems fails and the shutdown process is 
delayed by 90 sec before the timeout takes over. So which one is the proper
After=... command remains unclear.
The only thing that invariably works without obstacles is to umount the sshfs
devices myself by hand right before issuing shutdown. I will attach a third
journalfile with a umount failure, run in the same conditions as journalfile nr
2.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20140117/fa1e1be6/attachment.html>


More information about the systemd-bugs mailing list