[Bug 668217] New: A NFS Client Boot Process and Shut-down are both Unacceptably Slow in the Absence of its NFS Server - NFS NON V4
https://bugzilla.novell.com/show_bug.cgi?id=668217 https://bugzilla.novell.com/show_bug.cgi?id=668217#c0 Summary: A NFS Client Boot Process and Shut-down are both Unacceptably Slow in the Absence of its NFS Server - NFS NON V4 Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: scott@aphofis.com QAContact: jsrain@novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.2.13) Gecko/20101203 SUSE/3.6.13-0.2.1 Firefox/3.6.13 Currently If boot a PC that has a NFS Client mount point and that NFS Server is Offline or not present; the boot process halts for a protracted time. The delay in booting the PC that cannot find its NFS Server, can add up to 12 or more seconds as the boot process stalls waiting to find its NFS Server - The delay in not finding the NFS Server takes so so long whilst it waits to find its NFS Server, but will give up and continue the boot process after say +30 Seconds. This bug report differs from previous ones as they may only have extended boot processes which do not include the same problem as a shutdown also occuresi n the above PC example This bug includes both extended boot AND shut-down processes of up to +30 Seconds QA. - I am not sure if this is a kernel matter - I seem to think so but will await your advise and specific requests from logs data QA - There may be a similar bug open on the protracted boot process but none also contain the shutdown period being effected as well! Reproducible: Always Steps to Reproduce: 1.Set-up both NFS Server and Client 2.Shut-down the NFS Server PC 3.Boot or shut-down the PC that has NFS Client - you will note the boot/shutdown log halts at both - Just use ESC for both splash screens Actual Results: Above Expected Results: Above Note X_64 Hardware and NOT NFS V4 - 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=668217 https://bugzilla.novell.com/show_bug.cgi?id=668217#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=668217 https://bugzilla.novell.com/show_bug.cgi?id=668217#c1 Neil Brown <nfbrown@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #1 from Neil Brown <nfbrown@novell.com> 2011-02-07 03:03:31 UTC --- This is normal and expected. It takes a while to confirm that a server is not present. If you want to avoid this you need to use an auto-mounter to mount (and unmount) the NFS filesystems. Then it will only try to mount once you try to access the filesystem. If a missing NFS server were delaying boot by several minutes, that might be an issue, but 30 seconds is normal. -- 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=668217 https://bugzilla.novell.com/show_bug.cgi?id=668217#c2 Scott Couston <scott@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |scott@aphofis.com Resolution|INVALID | AssignedTo|nfbrown@novell.com |bnc-team-screening@forge.pr | |ovo.novell.com --- Comment #2 from Scott Couston <scott@aphofis.com> 2011-02-07 04:12:12 UTC --- NO other Application or file Manager cause delay off any type. - Wrong Tested under complete and accessible NFS Server and Client eliminated out of the issue. I can easily see how instant it take to use a File Manager of NFS Drive - It has no lag time what-so-ever When it comes to OOO, the creation, over right by Save File or creation of a new file over NFS. Can you tell me what were your finding under the quotes test condition??? If you have made a guess rather than than test as above conditions indicate, your entry into this bug is ludicrous, I am sorry to say that you are conducting yourself without creditability nor respect by a single ignorance statement Neil - We may be an OpenSource Project, but high stands of our products it what sets us apart! I have pride, many have pride, we all treat this professionally....Having the send person close without any single piece of accurate information is NOT Quality -- 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=668217 https://bugzilla.novell.com/show_bug.cgi?id=668217#c3 Neil F Brown <nfbrown@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED CC| |nfbrown@novell.com Resolution| |INVALID --- Comment #3 from Neil F Brown <nfbrown@novell.com> 2011-02-07 04:58:51 UTC --- I'm sorry, but I cannot make out what you are trying to say. Any mention of a file manager or OOo or 'save file' seems completely off-topic given the original problem description. The problem description is about boot up and shutdown. If a client is configure to mount an NFS filesystem at boot time by having an entry in /etc/fstab, then it will try to mount that filesystem at boot time. If the 'bg' option is not given it should block indefinitely until the server responds. If the 'bg' option is given, it will try for a few seconds (I don't remember how much - 10 to 30 sounds likely) and then fork and continue trying in the background while the system goes on to do other things. So you would expect a delay during boot up. during shutdown, the client will attempt to tell the server that the filesystem has been unmounted. This is actually fairly pointless but the protocol requires it so we do it and it is rarely a problem. We don't wait forever though - just 10 to 30 seconds and then move on. I'm sorry if you didn't think my original response was accurate. I assure you that I believe it is, and I hope this extra information will help you - either to understand what is happening, or to explain your situation more clearly if I have misunderstood it. -- 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=668217 https://bugzilla.novell.com/show_bug.cgi?id=668217#c4 Scott Couston <scott@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aj@novell.com, | |rhaidl@novell.com --- Comment #4 from Scott Couston <scott@aphofis.com> 2011-02-07 09:38:28 UTC --- As I stated - Only under X_64, OOO takes an inordinate time to use its default file manager to 'save as' or 'save (over-write) to a NFS Drive - NOT V4 As I stated Only under X64, OOO takes an inordinate time to use its default file manager to find and retrieve a file from NFS Drive. The issues at hand are huge. 1. The X64 NFS Drive NON V4, despite its root kill and rw attributes applied to the NFS drive may have the cause of this problem. 2. The X64 version of OOO on our default packing list has issues with the X_64 Kernel or itself. 3. The xlurunner will still need modification - As I stated - I cannot offer anything to show you - No Logs nor wait time of up to 60-90 Seconds. In in the detection we say its 100% reproducible that is what we mean. It means you can recreate the exact Problems. In closing this bug as invalid can you please enter your own observations that made your test go through without errors - This is useful info. I asked QA to consider the many and varied classifications this problem could easily fall into! BNC Screening just vets out completely ilogical bugs or ones that need clarification before assignment. As he's the Quality Manager, QA decides final internal priority, assignment and various needinfo of sometimes many staff to just get the bug narrowed down to the right assignee and classification Jiri - Please leave this as invalid, however could you please spend some time as Quality Manager on the above issue. - Re-Set to Defaults and no further action on my part - Thanks Jiri - -- 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=668217 https://bugzilla.novell.com/show_bug.cgi?id=668217#c5 --- Comment #5 from Scott Couston <scott@aphofis.com> 2011-02-07 09:38:53 UTC --- I'm off for 4 months leave and sanity break - going skiing in Canada as its so stinking hot here in OZ -- 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=668217 https://bugzilla.novell.com/show_bug.cgi?id=668217#c6 --- Comment #6 from Scott Couston <scott@aphofis.com> 2011-02-07 11:17:48 UTC --- No Confidence if fixability -- 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=668217 https://bugzilla.novell.com/show_bug.cgi?id=668217#c7 Scott Couston <scott@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #7 from Scott Couston <scott@aphofis.com> 2011-02-07 11:30:46 UTC --- No confident is enthusiasm which by weekend made me take a break off to camads nice sjiiling If I canthe reject by as it retards in bugs that as important values ans still have very poring offeent back in 10.1 If I can get one single person, who can manage they entire Network connections refrigeration - via Network Manager - Please help my so very much -- 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=668217 https://bugzilla.novell.com/show_bug.cgi?id=668217#c8 Scott Couston <scott@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |669817 --- Comment #8 from Scott Couston <scott@aphofis.com> 2011-02-07 11:41:38 UTC --- With so may parts to this and 2 x final, invalid - you can p,ease for give -- 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=668217 https://bugzilla.novell.com/show_bug.cgi?id=668217#c9 Scott Couston <scott@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |660453 --- Comment #9 from Scott Couston <scott@aphofis.com> 2011-02-08 20:55:09 UTC --- Again Sorry for cut and Paste error in #8 - Clean up as needed - Apparently there is NO issue see #1 #3 and I have little confidence in the above to continue to add any more of my time - -- 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=668217 https://bugzilla.novell.com/show_bug.cgi?id=668217#c10 --- Comment #10 from Scott Couston <scott@aphofis.com> 2011-02-08 20:56:56 UTC --- RE Error in #7 due bad copy and paste - However inaction by #3 is of the poorest management of bugs - The status shown in #3 will remain - -- 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=668217 https://bugzilla.novell.com/show_bug.cgi?id=668217#c Scott Couston <scott@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |704797 -- 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