[Bug 851020] New: autofs(nfs) and wifi(NM) are brought down/up in the wrong order for suspend/hibernate
https://bugzilla.novell.com/show_bug.cgi?id=851020 https://bugzilla.novell.com/show_bug.cgi?id=851020#c0 Summary: autofs(nfs) and wifi(NM) are brought down/up in the wrong order for suspend/hibernate Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: hp@lisa-gmbh.de QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 Hi, when suspending/hibernating my wife's notebook with 13.1 GM, autofs is shut down after wifi, which is a pitty, since she has some autofs mounts running. Net result: it takes several minutes to suspend, as it will wait for nfs timeouts. Consequently on resume, autofs cannot start correctly, since wifi is missing. Some progress is noticable in this area, since older releases failed to start autofs at all. Wifi device is configured in NetworkManager as system connection and starting at boot. Reproducible: Always Steps to Reproduce: 1. Enable /net in /etc/auto.master 2. Create a system NM wifi connection, started on boot 3. suspend Actual Results: Long delay, before it finally suspends correctly. Expected Results: Immediate suspend (well, after autofs unmount at least) -- 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=851020 https://bugzilla.novell.com/show_bug.cgi?id=851020#c Xiyuan Liu <xyliu@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xyliu@suse.com AssignedTo|bnc-team-screening@forge.pr |lchiquitto@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=851020 https://bugzilla.novell.com/show_bug.cgi?id=851020#c1 --- Comment #1 from Hans-Peter Jansen <hp@lisa-gmbh.de> 2013-11-20 15:30:34 UTC --- I take back the second part. The order is correct on resume. BTW, I work around this issue by abstain from autofs and do the mounts via fstab. -- 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=851020 https://bugzilla.novell.com/show_bug.cgi?id=851020#c2 Aaron Digulla <digulla@hepe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |digulla@hepe.com --- Comment #2 from Aaron Digulla <digulla@hepe.com> 2014-01-15 20:58:06 UTC --- Same problem with NFS and normal shutdown: Network is stopped and then the system tries to unmount NFS shares -> deadlock. Current workaround: I created a script /etc/sysconfig/network/if-down.d/nfs-umount ------------ nfs-umount --------------------- #!/bin/bash [ "$2" != "lo" ] || exit 0 echo "Unmounting NFS..." umount -av -t nfs ------------ nfs-umount --------------------- This solves the issue (also when suspending) but during resume, the shares aren't mounted again. My guess is that there is something wrong with the order in which systemd (or whatever controls the system startup) invokes the scripts. -- 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