[Bug 857970] New: systemd mounts nfs shares on startup, but forgets to umount them before network shutdown
https://bugzilla.novell.com/show_bug.cgi?id=857970 https://bugzilla.novell.com/show_bug.cgi?id=857970#c0 Summary: systemd mounts nfs shares on startup, but forgets to umount them before network shutdown Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: ohering@suse.com QAContact: qa-bugs@suse.de Found By: Outsourced Testing Blocker: --- Created an attachment (id=573753) --> (http://bugzilla.novell.com/attachment.cgi?id=573753) 13.1-nfs-mount-shutdown-hang.txt 13.1 with xfce desktop. I copied the fstab from another partition, it contains also a nfs entry: IP:/share/dir /local/dir nfs soft,intr,tcp,bg,vers=3 0 0 For some reason this nfs entry gets mounted automatically, I did not do anything regarding nfs. But during 'init 6' or 'init 0' the network is stopped before that nfs share is umounted. As a result the system hangs forever at the end of the shutdown, because IP does not respond. No surprise, the network is down already! So whatevers does the automounting of such nfs share must also take care of autoumounting it before the network disappears. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=857970 https://bugzilla.novell.com/show_bug.cgi?id=857970#c Xiyuan Liu <xyliu@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xyliu@suse.com AssignedTo|bnc-team-screening@forge.pr |systemd-maintainers@suse.de |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=857970 https://bugzilla.novell.com/show_bug.cgi?id=857970#c1 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |systemd-maintainers@suse.de Component|Basesystem |Network AssignedTo|systemd-maintainers@suse.de |bnc-team-screening@forge.pr | |ovo.novell.com --- Comment #1 from Dr. Werner Fink <werner@suse.com> 2014-02-14 10:30:27 UTC --- Isn't that already fixed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=857970 https://bugzilla.novell.com/show_bug.cgi?id=857970#c Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |nfbrown@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=857970 https://bugzilla.novell.com/show_bug.cgi?id=857970#c2 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |mt@suse.com --- Comment #2 from Neil Brown <nfbrown@suse.com> 2014-02-17 03:03:47 UTC --- I think this problem should be handled by network-online.target forming a barrier between the remote mounts and the network interfaces. i.e network interfaces are started Before network-online.target and remote mounts are started After network-online.target On shutdown these are interpreted in reverse, so network interfaces will be stopped After network-online.target remote mounts will be stopped Before network-online.target On my test VM, the second of these conditions is met, the first is not. So I experience the same hang that you do. I edited /usr/lib/systemd/system/network@.service and added Before=network-online.target and the hang went away. I think this is a correct fix. If there is some other systemd unit which starts (and stops) network interfaces, then it needs to ordered Before=network-online.target too. Marius: do you look after sysconfig-network? Can you take this? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=857970 https://bugzilla.novell.com/show_bug.cgi?id=857970#c3 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|mt@suse.com | Resolution| |DUPLICATE --- Comment #3 from Dr. Werner Fink <werner@suse.com> 2014-02-17 07:56:07 UTC --- The this is a dup of bnc #857031 *** This bug has been marked as a duplicate of bug 857031 *** http://bugzilla.novell.com/show_bug.cgi?id=857031 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com