[Bug 456358] New: prematurely shutdown of nic during shutdown
https://bugzilla.novell.com/show_bug.cgi?id=456358 Summary: prematurely shutdown of nic during shutdown Product: openSUSE 11.1 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: hwit@a-domani.nl QAContact: qa@suse.de Found By: Beta-Customer When doing a reboot of the system (RC1), the system gets in a deadlock, waits forever can not correct it at that point. One can only "pull the plug" reason: First you see a message: shutting down nics And some line later you get: Shutting down NFS-client Obviously the last one fails, as the network is allready down tmp-work-around: umount -a -t nfs BEFORE shutdown/reboot is done (probably missing/wrong dependency) -- 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=456358
Cyril Hrubis
https://bugzilla.novell.com/show_bug.cgi?id=456358
User nfbrown@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=456358#c1
Neil Brown
https://bugzilla.novell.com/show_bug.cgi?id=456358
User mt@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=456358#c2
Marius Tomaschewski
A fix to cause nfs-client not to hang if the network is down went in just after -rc1. So in the final release it should not hang.
Whether it is appropriate for the network to be shutdown before NFS I am not certain. I suspect this is related to /etc/init.d/network-remotefs which is stopped before 'nfs' - where as /etc/init.d/network is stopped afterwards.
Yes, there are interfaces that are supported only with mounted $remotefs (nfs or smbfs, see /etc/insserv.conf) because of /usr on NFS. These interfaces (e.g. wlan) are stopped by network-remotefs before nfs is going down. An interface that is generally supported also on localfs only, may be started/stopped in network-remotefs too, when there are dependencies to an unsupported interface, e.g. a bridge (supported) that contains a tap or wlan port interface that needs remotefs. Generally, when an interface is started in "localfs" flow, it will be also stopped in "localfs" flow. Same in "remotefs" case. This also means, that when the start of network + nfs was fine, there should be no reason why the stop should fail or make problems. The bug 447098 mentioned above, fixes virtual interface stop&start order (e.g. bridge started before a tap) -- in network-remotefs case, and may be the reason. The most actual package (as on 11.1 GMC + a [s390] migration fix) is available at: http://download.opensuse.org/repositories/home:/mtomaschewski:/Factory/openS... You can try out if it helps. When not, please boot your system as usual. Then call on the command line: mount > /tmp/bug456358.out 2>&1 ip r s >> /tmp/bug456358.out 2>&1 /etc/init.d/nfs stop >> /tmp/bug456358.out 2>&1 /etc/init.d/network-remotefs stop -o boot debug >> /tmp/bug456358.out 2>&1 ip r s >> /tmp/bug456358.out 2>&1 /etc/init.d/network stop -o boot localfs debug >> /tmp/bug456358.out 2>&1 and provide the output off all this, that is the /tmp/bug456358.out file. -- 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=456358
User mt@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=456358#c3
--- Comment #3 from Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=456358
User hwit@a-domani.nl added comment
https://bugzilla.novell.com/show_bug.cgi?id=456358#c4
--- Comment #4 from Hans Witvliet
https://bugzilla.novell.com/show_bug.cgi?id=456358
User mt@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=456358#c5
Marius Tomaschewski
participants (1)
-
bugzilla_noreply@novell.com