[Bug 707898] New: A NFS Client Boot Process and Shut-down are both Unacceptably Slow (+12 Minutes) in the Absence of its NFS Server - NFS NON V4
https://bugzilla.novell.com/show_bug.cgi?id=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c0 Summary: A NFS Client Boot Process and Shut-down are both Unacceptably Slow (+12 Minutes) 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: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: scott@aphofis.com QAContact: jsrain@novell.com CC: aj@novell.com, roland.haidl@suse.com, nfbrown@novell.com, scott@aphofis.com Found By: System Test Blocker: --- +++ This bug was initially created as a clone of Bug #668217 as clarity needs to be established for my previous wayward cut and paste of extraneous information - My Apologies Jiri- Too many bugs open on too many screens - Again my Apologies+++ 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 minutes 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 +12 minutes 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 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 - The issue is the delayed boot process which is greater than 12 MINUTES Expected Results: There should be only a limited time-out value of less than 30 seconds and not 12 minutes which is the case - Hence this bug 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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c1 --- Comment #1 from Scott Couston <scott@aphofis.com> 2011-07-25 23:18:54 UTC --- *** Bug 704797 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=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.
https://bugzilla.novell.com/show_bug.cgi?id=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c zj jia <zjjia@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zjjia@novell.com AssignedTo|bnc-team-screening@forge.pr |mvidner@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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c2 Lukas Ocilka <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |locilka@suse.com InfoProvider| |nfbrown@suse.com --- Comment #2 from Lukas Ocilka <locilka@suse.com> 2011-09-14 09:15:47 UTC --- Neil, is there anything that YaST could do about NFS Client waiting for unreachable NFS Server, e.g. to set a configurable time-out? Is that actually wanted? -- 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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c3 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|nfbrown@suse.com | --- Comment #3 from Neil Brown <nfbrown@suse.com> 2011-10-10 00:18:29 UTC --- There are a few different issues here. Firstly it is not clear to me that an NFS mount request should time out particularly quickly. The fact that you list a mountpoint in /etc/fstab suggests that you need that filesystem mounted for successful operation, so there might be no point continuing if it is not mounted. If you don't really need the filesystem but would just like it there if possible, then the correct way to request that is to use the "bg" mount option, or to use an automounter. So it probably makes sense fort YaST to suggest, or at least allow, the 'bg' option to be set for mountpoints that are created -- or perferably it should configure an automounter and use that for NFS. That said, there is a bug in the kernel relating to NFSv4 mounts that I haven't managed to get to the bottom of yet. If the server that is not responding is on a different subnet, the ICMP error message which comes back to say "cannot get there from here" gets ignored and we get a long timeout. Also NFSv4 mounts don't seem to reduce the timeout when 'bg' is set. However as you are not using V4 you can avoid this by explicitly requesting 'v3'. So you should be able to reduce the timeout significantly by specifying options "bg,vers=3". Also I think 11.4 has some better timeouts than 11.3, so if changing the options doesn't help, an upgrade might. YaST could help by allowing, or even encouraging, the 'bg' option to be specified (if it doesn't already) and also explicitly setting the NFS version to be used. Bug #679059 covers the issues that NFSv4 mounts don't respond to ENETUNREACH properly, though I'm not sure if this is the case here. If you still have problems and want more analysis, please run mount with "-v" and report the output, and also use "tcpdump -w /tmp/somefile -s 0 host $SERVERIP" to collect a network trace, and attach that. -- 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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c4 --- Comment #4 from Scott Couston <scott@aphofis.com> 2011-10-10 10:58:03 UTC --- Created an attachment (id=455348) --> (http://bugzilla.novell.com/attachment.cgi?id=455348) Image 1 of 2 Forgive my intrusion her between the discussion of Lukas and Neil. This bug title is about a NON NFS V4. With NFS V4 Yes the Kernel does all the Magic. Neil, on a non NFS V4 we just need a time out of 10 seconds on the boot process and a cron job to reassess if the NFS drive, that was absent is now available, if so; Mount it. When booting there is a time-out for a DHCP IP to come online, why not with NFS NON V4 - Same code. Its not much simpler than that that I would suggest...Luckas your thoughts. Neil, while your looking at Mounts, how about giving NFS Client the ability to find a NFS Server without entering the IP - It has never been possible since 10.0 to use the choose button to find anything - See attached -- 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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c5 --- Comment #5 from Scott Couston <scott@aphofis.com> 2011-10-10 10:58:50 UTC --- Created an attachment (id=455350) --> (http://bugzilla.novell.com/attachment.cgi?id=455350) 2 of 2 -- 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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c6 Martin Vidner <mvidner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low Status|NEW |ASSIGNED Summary|A NFS Client Boot Process |[yast2-nfs-client] suggest |and Shut-down are both |bg mount option to avoid |Unacceptably Slow (+12 |overlong timeouts |Minutes) in the Absence of | |its NFS Server - NFS NON V4 | Severity|Major |Normal --- Comment #6 from Martin Vidner <mvidner@suse.com> 2011-10-10 15:33:11 CEST --- Thank you Neil! -- 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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c7 --- Comment #7 from Neil Brown <nfbrown@suse.com> 2011-10-10 22:33:11 UTC --- Hi Scott, I realise that the bug description said "non-nfs v4". I suspect that just means that you explicitly didn't say that you wanted nfsv4. However when mount.nfs attempts to mount something it will still try NFSv4 first unless it has been explicitly told to try some other version. The fact that you didn't tick the "NFSv4 share" box doesn't mean that NFSv4 will not be attempted at mount time. (I'm don't know what it does mean, but I'm fairly sure it isn't that). So you still the get longer timeout that the current NFSv4 code imposes unless /etc/fstab explicitly contains "vers=3" or similar. NFS and DHCP are totally different code bases with different histories and different priorities. You might think it should work some particular way, and I have no desire to argue about that. However the way that it *does* works is: 1/ If you want a filesystem mounted at boot time, you list it in /etc/fstab, and possibly have to wait a while if the server isn't responding. 2/ if you want a filesystem mounted as soon as possible after boot time, you put it in /etc/fstab and add the 'bg' mount option. 3/ If you want a filesystem mounted at the time when you actually use it (in most cases the sensible approach) you configure an auto-mounter. Who you communicate these desires to yast is not something I can help with - probably Martin can. If the "choose" button does not work for you, I suggest you submit a bug report. It works for me. It works by broadcasting a 'ping' to any rpc.mountd program on any host on the same subnet. I would get, based on the fact that this doesn't work for you, and the fact that your are getting long timeouts, that your server and your client are on different subnets. It is not possible to broadcast to other subnets, so not possibly to discover servers on different subnets. If you could report the output of "ifconfig" on the main network interface of each of your client and your server, I could see if this is the case. NeilBrown -- 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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c8 --- Comment #8 from Scott Couston <scott@aphofis.com> 2011-10-10 22:49:21 UTC --- Thanks Neil for your helpful incite. My only hope is that this wait issue get solved. The muchanism to achieve this is yours - Your at he coal face and know whats happening in the future so the fix for this wait issue is at your discretion on how to do so. All users face this issue, but and very few have networks to use most all network services, they dont get reported. This fix is yours to achieve, eloquently via the best method. The user just wants it to work by default using the Yast interface and needs the huge time large to finish. With respect to the Choose Button not working. I have bug reported it since 10.0 more than 10 times with no resolution. Every user knows full well, including myself, that as far as Yast is concerned is a closed shop. User land chatter reflects that user bugs of yast are unlikely to ever be solved, fixed or enhanced - Goes to the logic of the amount of bugs raised about the choose button never working despite the years since 10.1 and many bug reports. Dont ever worry about being rude, I never take anything personally and text is the poorest way, to describe frustrating bugs without seemingly being rude. Its all cool mate! Scott -- 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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c9 --- Comment #9 from Scott Couston <scott@aphofis.com> 2011-11-03 21:59:45 UTC --- It does offcourse get ugly when in the above example both PC's are NFS Servers and NFS clients...who waits for who to load??? -- 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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c10 --- Comment #10 from Scott Couston <scott@aphofis.com> 2011-11-30 21:49:22 UTC --- I will attach the yast logs for both NFS client and server. Could you please tell me by return the name and location of the login scrip. Its dreadful that a timeout is displayed on the screen after about 4 minutes, and after the login script reports 'time out' the PC then continues to stall for another 5 minutes. We need an elegant solution to this problem. My LAN has only 8 PC's but image the waste of time on a much larger LAN - This is worse than turn the PC on in the morning and make a coffee....Its more like go away and cook bacon and eggs and toast and eat it before returning to your PC. Can we refine and elegant solution by added NFS Server and Client connections to the kernel and have it make frequent checks to see any NFS Server either new or old that is advertising or has halted. In the same login can we also let the kernel perform checks of NFS Clients which appear as PC's boot and disappear when the PC is halted. I think we need to get rid of sm-notify completely, every time a change is made to it it gets worse with new errors and new problems. -- 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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c Scott Couston <scott@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |727870 -- 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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c11 Scott Couston <scott@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |mvidner@suse.com --- Comment #11 from Scott Couston <scott@aphofis.com> 2011-12-20 08:46:01 UTC --- mvidner@suse.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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c12 Scott Couston <scott@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|YaST2 |Kernel AssignedTo|mvidner@suse.com |kernel-maintainers@forge.pr | |ovo.novell.com QAContact|jsrain@suse.com |qa@suse.de --- Comment #12 from Scott Couston <scott@aphofis.com> 2011-12-25 09:37:56 UTC --- This is a kernel issue with NFS...Please specify the files you need for both login and logout script and their corresponding audit results. As for the the browse for a NFS Client not working via host name but always working for an IP - Its been an issue for me since 10.0 and if yours works o.k then it must be o.k...I have another bug on that issue..:-) -- 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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c Scott Couston <scott@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |739077 -- 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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c13 Scott Couston <scott@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|mvidner@suse.com | --- Comment #13 from Scott Couston <scott@aphofis.com> 2012-01-15 05:41:42 UTC --- Created an attachment (id=471276) --> (http://bugzilla.novell.com/attachment.cgi?id=471276) NFS Client Logs Please request any other log files accurately _ I dont like uploading so many monumental errors its that frightening -- 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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c Bug 707898 depends on bug 727870, which changed state. Bug 727870 Summary: Every FIND or BROWSE or LOCATE button that is meant to late another PC's Services has never Worked http://bugzilla.novell.com/show_bug.cgi?id=727870 What |Old Value |New Value ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Status|NEEDINFO |NEW Status|NEW |NEEDINFO Status|NEEDINFO |NEW Status|NEW |RESOLVED Resolution| |INVALID -- 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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c Bug 707898 depends on bug 727870, which changed state. Bug 727870 Summary: Every FIND or BROWSE or LOCATE button that is meant to late another PC's Services has never Worked http://bugzilla.novell.com/show_bug.cgi?id=727870 What |Old Value |New Value ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | -- 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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c14 --- Comment #14 from Scott Couston <scott@aphofis.com> 2012-02-06 10:17:57 UTC --- The other issues I have been testing of late are also 100% reproducible and relate to ANY situation where both or only the NFS Server PC and/or the NFS Client PC have not been totally shutdown when S2RAM and/or S2Disk has been used. Despite the NFS Server being re-established before its NFS Clients, no NFS Server/Client relationship is ever remounted and fails completely. In this situation the NFS Client will hang at sm-notify until the same huge time-out of in excess of 5 minutes has elapsed. In this situation where the PC is left to time-out NO NFS Client services are EVER reinstated. This is as much the fault of the NFS Server as well al its NFS Client. Where both Server and Client are both halted by S2RAM Or S2Disk and then resumed, NO NFS Services what-so-ever are ever re-established. If you need more log data regarding this test please be specific. AJ........Given this new test where NO NFS Services what-so-ever are recreated please reassess the assigned priority...This goes from bad to worse guys...sorry -- 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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c15 Jeff Mahoney <jeffm@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEW AssignedTo|kernel-maintainers@forge.pr |nfbrown@suse.com |ovo.novell.com | --- Comment #15 from Jeff Mahoney <jeffm@suse.com> 2012-03-05 22:05:44 UTC --- 11.3 is out of maintenance. If you can reproduce this issue with 11.4 or 12.1, please re-open and adjust the Product field to reflect the latest version affected. -- 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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c16 Scott Couston <scott@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |scott@aphofis.com --- Comment #16 from Scott Couston <scott@aphofis.com> 2012-03-06 00:26:13 UTC --- Jeff - No problems testing in 12.x as I know this is still an issue for this and dependencies - Is it more helpful to give you log details for dependencies before I upgrade the software version...Let me know..Thanks mate:-) -- 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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c17 Scott Couston <scott@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|scott@aphofis.com | --- Comment #17 from Scott Couston <scott@aphofis.com> 2012-03-06 00:26:40 UTC --- OOOPS ! -- 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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c Bug 707898 depends on bug 727870, which changed state. Bug 727870 Summary: Every FIND or BROWSE or LOCATE button that is meant to late another PC's Services has never Worked http://bugzilla.novell.com/show_bug.cgi?id=727870 What |Old Value |New Value ---------------------------------------------------------------------------- Status|REOPENED |CLOSED Resolution| |NORESPONSE -- 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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c Bug 707898 depends on bug 727870, which changed state. Bug 727870 Summary: Every FIND or BROWSE or LOCATE button that is meant to late another PC's Services has never Worked http://bugzilla.novell.com/show_bug.cgi?id=727870 What |Old Value |New Value ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Resolution|NORESPONSE | -- 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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c18 Scott Couston <scott@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |Kernel Version|Final |RC 2 Product|openSUSE 11.3 |openSUSE 12.1 Target Milestone|--- |Final --- Comment #18 from Scott Couston <scott@aphofis.com> 2012-03-09 06:03:35 UTC --- Same Issue as in 12.1 - The Kernel in 11.3 is the same in 12.1 is it not??? None the less this bug is valid also in 12.1 -- 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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c Scott Couston <scott@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks|739077 | Depends on|727870 | -- 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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c19 Scott Couston <scott@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Component|Kernel |Kernel Version|RC 2 |Factory Resolution| |FIXED AssignedTo|nfbrown@suse.com |kernel-maintainers@forge.pr | |ovo.novell.com Product|openSUSE 12.1 |openSUSE 11.4 --- Comment #19 from Scott Couston <scott@aphofis.com> 2012-04-24 23:18:00 UTC --- Due to the inordinate problems I have with 12.1 I have reverted back to 11.4 where this problem first started. I am happy to report all issues with NFS sm-notify have been resolved -- 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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c20 Scott Couston <scott@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Resolution|FIXED | AssignedTo|kernel-maintainers@forge.pr |scott@aphofis.com |ovo.novell.com | --- Comment #20 from Scott Couston <scott@aphofis.com> 2012-04-30 06:57:54 UTC --- Created an attachment (id=488778) --> (http://bugzilla.novell.com/attachment.cgi?id=488778) May be a repeat of existing logs My apologies for the confusion, The bug is NOT fixed in 11.4 which log data will revile. I can only state that it still exists in 12.1 but I do not have the logs. I have attached more log info...This NFS waiting to time-out and then waiting for the time-out to time-out can easily add up to 3 minutes to the boot process on a X_64 4 x Core running at 3,598.63 MHz with 8GIG Physical RAM. If the NFS Server is not present at NFS client boot PC, it NEVER EVER will mount the NFS Server drive retrospectively -- 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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c21 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |scott@aphofis.com --- Comment #21 from Neil Brown <nfbrown@suse.com> 2012-04-30 07:54:59 UTC --- Hi Scott, I must confess that I've lost track of exactly what "This bug" is. You have mentioned problems with booting with resuming from suspend. You've mentioned mount being slow and sm-notify being slow. Maybe these are all all true. But we need to focus to be able to find a solution. So let's focus on: If the NFS Server is not present at NFS client boot PC, it NEVER EVER will mount the NFS Server drive retrospectively. That is correct and by design - there is no bug there. If you want to be able to boot while and NFS server it not available you have two options: 1/ add the 'bg' option in /etc/fstab for the NFS mounts. This will cause 'mount' to continue retrying the mount in the background without holding up the mount process. 2/ use and auto-mounter to only try to mount filesystems one demand. Have you tried one of these? What was the result? -- 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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c22 Scott Couston <scott@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|scott@aphofis.com | --- Comment #22 from Scott Couston <scott@aphofis.com> 2012-05-06 09:39:49 UTC --- Agree...YES!...but all options no matter what stall the boot process out to an inordinate amount of time..This is reproducible!!! On the other matter, yes it would be nice to retro mount NFS drives as they become available and I would have thought that if the Kernel was running the show it would be done...but I take it the kernel just calls sm-notify -- 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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c23 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |scott@aphofis.com --- Comment #23 from Neil Brown <nfbrown@suse.com> 2012-05-06 10:00:14 UTC --- Hi Scott, I cannot help you unless you give details. I ask you a question in Comment #21 - Did you try 1/ or 2/ ? If so, what was the result? If you cannot give clear answers, then I cannot help you. The kernel doesn't call sm-notify. sm-notify runs to tell other hosts that this one has rebooted. It is used to clear out old locking state. It is quite separate from mounting and should not cause any delays. Do you believe sm-notify is causing a delay to boot? If so, what evidence do you have for 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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c24 Scott Couston <scott@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|scott@aphofis.com | --- Comment #24 from Scott Couston <scott@aphofis.com> 2012-05-06 23:16:31 UTC --- Only too happy to provide info...Yes I have tried both options on sm-nofity and I currently have them on my personal workstation. I would like to upload the historical boot processes so you can see the options and time-outs yourself. Can you please let me know what files I can upload so you can see the same. How else can I help you as I have these problems on a production PC?? As this bug was reclassified to kernel from yast or update problems, my assumption was that sm-notify must be connected - My apologies for drawing the wrong assumption. I now understand that sm-notify is a sole process on boot when there are NFS mounts in 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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c25 Scott Couston <scott@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|scott@aphofis.com |kernel-maintainers@forge.pr | |ovo.novell.com --- Comment #25 from Scott Couston <scott@aphofis.com> 2012-05-10 11:29:09 UTC --- Jerry and Geoff (forgot Geoff email) - please insert)could you please figure what happening to all these major related bugs..Network drives falling off her and there, or are never there or only there when we (the staff) the boot sequence of each PC - details under as all these issues are about Yast, dont know how 1. the bug was assigned to me and 2. why its not yast as I have been told the kernel attempts NO retrospection connections of past and present as a standard Krone action, but has been left as a kernel issue Can you please let me know what files I can upload so you can see the same. How else can I help you as I have these problems on a production PC?? To put this in a real-time scenario - I have 10 staff who each have a Linux PC, there is a file server that all staff need to save their work on, but not always. - A 10 to 1 File NFS Server waiting until it has booted before the staff can beet their PC. Now all workstations have NFS Servers to the Backup server via NFS which backups the /home directory of each user and the file server. I have a VERY LARGE MAP IN MY OFFICE IN WHICH THE STAFF OR MACHINES NEED TO BOOT IN THE CORRECT ORDER...AND IF ANYONE HAS SUSPEND pc OVER LUNCH TIME THE nfs DRIVE MAY OR MAY NOT COME BACK... Please let me know of what files to upload that hold my login scripts.......they will all be there...Also I separated dependants with previous BUGS ,not because they all suffer the same download probes, but have dependant bug in PMS seems to frighten a lot of analysts...cheers So please I need you to let me know what the archived login script file would want please. bottom line, if you are not going to try to fix it due - priority or something - please just bury this request without email contacts and rename it tinto the impossible home repository -- 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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c26 Scott Couston <scott@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |WONTFIX --- Comment #26 from Scott Couston <scott@aphofis.com> 2012-05-13 04:43:53 UTC --- Despite this bug has been there for ONE+r years with log files back and too NOTHING WAS DOE TO CORRECT THIS. It was closed by the reporter as WONTFIX DUE FACTS ALL CONTAINED here how apparent no resources were ever going to be allocated for solution. Suse needs 'A problem Manager, a Integrated Problem management Database and allocation of expected result along the line that leads to the bug being fixed. The problem managers is get solved as many bugs as possible even if they have to cary a big stick and at its highest , problem at the highest form be a major problem at site - That classifications should call all resources working out 24/7 to solve the problem and to have a autopsy why it failed at site...etc. etc. etc. The Problem Manager of which we have none, nor any classification on how the bug effects only site, site distro'd, only versions, only architecture should and the PM Must have teat - Just like in standard commercial companies -- 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=707898 https://bugzilla.novell.com/show_bug.cgi?id=707898#c27 Scott Couston <zcnnnnzc@virginbroadband.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zcnnnnzc@virginbroadband.co | |m.au Resolution|WONTFIX |FIXED --- Comment #27 from Scott Couston <zcnnnnzc@virginbroadband.com.au> 2012-10-07 05:00:49 UTC --- I can report that this bug has been fixed in 11.4 after applying new online updates. I cannot work out which update fixed this as there are so many that has made 11.4 the most stable in the whole history of opensuse -- 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