https://bugzilla.novell.com/show_bug.cgi?id=819515 https://bugzilla.novell.com/show_bug.cgi?id=819515#c0 Summary: Non NFS V4 Mounts Stall the Boot Process for Minutes upon Minutes Until Huge Value Time-outs Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain@suse.com ReportedBy: secure@aphofis.com QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 The new boot loading and starting of services has gone back to stalling when it is unable to mount a NFS Drive when that Device is not running. We had this problem in 11.1/11.2/11.3/11.4...At version 11.4 the mount options were changed from default to massively decrease the time out value and to basically ignore the device IP if it could not be reached. Currently on an X_64 Quad Core the time out period is in excess of 5 minutes ontop of other services being started which are lightening fast. If I didn't know better I would swear the PC had frozen and no fancy SysRqs Key lets you halt or bypass or shutdown the PC. I would think most just reset the hardware and go make a cup of coffee whilst it loads the services again You can ESC the splash screen showing the service started but stalled looking for the NFS device. With or Without the splash screen the very long timeout creates the feeling the PC has frozen especially as the list of other services run like lightening. I dont know why we are back at 11.1 where this issue was first reported. I dont know if the developers there have ANY NFS drives on their PC's but I can assure you they dont as this error sticks out like...well you know. Reproducible: Always Steps to Reproduce: 1.Create a NFS non V4 2.Boot the PC when the NFS drive's PC is not operating on the Network 3.ESC from the boot splash screen Actual Results: The fast boot is wonderful and the starting of services wonderful.....except where there is a service that cannot complete...Its more than the excessive timeout with NFS. The same is true if ANY of the services started at boot are not present Expected Results: Time to put NFS into the kernel for good so it can constantly retry to connect to a NFS server when ever it comes online. The mounting of network drives must be the responsibility of the kernel I really think if you want my opinion. When any of the services are loading and any fail, I think we ask the user very quickly that there is an issue..."continue or skip option window" There's a whole lot of bugs in 12.2 that are on NEW satus which are probably directly related to this issue and probably more who think their PC is just freezing on Boot. I was going to update the dependencies but thought better as so many of the current bugs appears to be related to this one. TELL ME PRECISELY what files you need as mounting of services during quick boot have changed things a little bit -- 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.