[Bug 659495] New: Boot Process will Hang Indefinitely if the Configured NFS Client Fails to find its Configured NFS Server
https://bugzilla.novell.com/show_bug.cgi?id=659495 https://bugzilla.novell.com/show_bug.cgi?id=659495#c0 Summary: Boot Process will Hang Indefinitely if the Configured NFS Client Fails to find its Configured NFS Server Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: scott@aphofis.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.2.12) Gecko/20101026 SUSE/3.6.12-0.7.1 Firefox/3.6.12 A NON NFS V4 Client boot process will hang the PC indefinitely after sm-notify is loaded when it cannot find its corresponding configured NFS Server Do NOT ask me for logs - This is 100% Reproducible and has been present as a bug since 10.3 - I just never bothered to log the Bug. IF you cannot reproduce - I can send the complete boot process text but this is unlikely Reproducible: Always Steps to Reproduce: 1. Configure a NFS Server without NFS V4 2. Configure a NFS Client without NFS V4 on a different PC 3. Shut-down the PC that has the NFS Server Configured 4. Restart the PC that has the NFS Client. The boot Process of this PC is as follows Eth1 IP address: 10.10.10.2/8 (MLTIVAC-010) (autoip) already configured eth1 Settng up service (localfs) Re-Starting syslog services Mount CIFS File System Starting rpcbind Starting auditd Starting kernel bases NFS server: mountd statd nfsd sm-notify Starting NFS client services: sm-notify Actual Results: After sm-notify is loaded, if it cannot find its NFS Server the boot process will hang indefinitely - There is NO Time-Out! Expected Results: With or Without locating a PC's NFS Corresponding Server the boot process should proceed as normal and NOT hang indefinitely! Currently the NFS Client PC is totally useless if it cannot locate its NFS Server via sm-notify - There is NO time out for sm-notify and the PC remains hug and virtually unusable. The PC running sm-notify us rendered useless in the above common situation -- 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=659495 https://bugzilla.novell.com/show_bug.cgi?id=659495#c wei wang <wewang@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wewang@novell.com AssignedTo|bnc-team-screening@forge.pr |nfbrown@novell.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=659495 https://bugzilla.novell.com/show_bug.cgi?id=659495#c1 Neil Brown <nfbrown@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #1 from Neil Brown <nfbrown@novell.com> 2010-12-15 01:18:47 UTC --- Can I suggest you add the 'bg' option in fstab so that the mount proceeds in the background if it is at all slow? I'm not 100% sure and don't have time to check just now, but I think the behaviour describe is deliberate by design. It is entirely possible that some files on the NFS filesystem are needed to complete the boot process so proceeding before it is mounted would be wrong. If you know that the filesystem is not essential for the rest of boot, you tell the system that with the 'bg' option. -- 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=659495 https://bugzilla.novell.com/show_bug.cgi?id=659495#c2 Scott Couston <scott@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |scott@aphofis.com --- Comment #2 from Scott Couston <scott@aphofis.com> 2010-12-15 04:42:48 UTC --- Thanks - I added the Option and its a bit faster to mount drives. I hardly think 'functioning as designed' is acceptable! The issue of a completely hung PC, and completely useless and with NO time-out, is in any way, shape or form acceptable...:-) No file on the NFS file system is required under many many tests. I'm only sharing a common directory well out of the way of the PC's root/boot/home directories. This has been the status since 10.3 - I just haven’t had the time to report it and passed it off as someone’s task to report it but very few users needs NFS in any shape at all. The priority stands as being totally accurate as well as the info I have provided - It is easily re-produced - Let me know in the unlikely even you cannot reproduce this - I really only report bugs that are 100% reproducible - Its easier for both of us....Many thanks :-) -- 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=659495 https://bugzilla.novell.com/show_bug.cgi?id=659495#c3 Neil Brown <nfbrown@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |INVALID --- Comment #3 from Neil Brown <nfbrown@novell.com> 2011-02-09 03:20:26 UTC --- There are two ways to automatically mount NFS filesystems 1/ List the filesystem in /etc/fstab. This tells the system that the filesystem *must* be mounted for boot to succeed. So if the server is it available, it waits. 2/ Use an automounter or 'autofs' to mount the filesystem. This tells the system that it is perfectly OK to boot where the server is not available. However any attempts to access the mountpoint will block or fail (Depending on automounter configuration) if the server is not accessible. (the 'bg' option is a poor alternative for autofs which was devised before autofs was developed). It seems to me that you want option 2, but are trying to use option 1. I strongly suggest you install 'autofs' and 'yast-autofs' and explore that option. (sorry for not replying sooner, I've had a very busy summer!) -- 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