[Bug 743969] New: Any loss of remote system operation with NFS active stops local drive access
https://bugzilla.novell.com/show_bug.cgi?id=743969 https://bugzilla.novell.com/show_bug.cgi?id=743969#c0 Summary: Any loss of remote system operation with NFS active stops local drive access Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86-64 OS/Version: openSUSE 12.1 Status: NEW Severity: Critical Priority: P5 - None Component: Mobile Devices AssignedTo: mobile-bugs@forge.provo.novell.com ReportedBy: johnlb2002@cox.net QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1 The remote system is 11.4 with XP dual boot. The local system is 12.1 with NFS to access three partitions. Normal operate works well, provided both continue to be up and running. If the 11.4 system gets rebooted to XP, the 12.1 system quits accessing local drives. This is with the normal connections set up with Yast and entries in fstab. If I remove the entries in fstab I can do manual mounts of the 11.4 system from the 12.1 system, and the 12.1 system continues to work when the NFS remotes are not available. The NFS system needs to time out rapidly, in seconds rather than many minutes per remote connection. Reproducible: Always Steps to Reproduce: 1.Mount the remote drives with Yast in fstab 2.Reboot, shut down, or lose power on the remote, or have wired or wifi connections be unstable. 3.Be frustrated by the local system acting like it crashed. Actual Results: Cannot read directories, open files, or save files. I also cannot effectively do a umount Expected Results: The system will notice that it gets no response, and will disconnect the broken NFS links, enabling local tasks to continue. -- 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=743969 https://bugzilla.novell.com/show_bug.cgi?id=743969#c1 Ned Ulbricht <nedu@netscape.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nedu@netscape.net --- Comment #1 from Ned Ulbricht <nedu@netscape.net> 2012-01-31 17:40:16 UTC --- Your description of the problem that you are having does not include sufficient details to exactly reproduce your setup. Beyond that, though, it appears to me that your expectations may not be in line with the documented behavior for NFS. Take a look at the nfs(5) man page, and note especially under "MOUNT OPTIONS" the options: "soft / hard". Pay extra attention to the "NB" warning about the risk of "silent data corruption" with use of the "soft" mount option. If, after reading the docs, you still think that you're encountering a bug, then you should provide more detailed information about your setup. Specifically: On the client, in the YaST2 dialog, in the "NFS Shares" tab: did you mark the "NFSv4 Share" checkbox? Did you specify any NFS "Options" or accept "defaults"? Please provide the fstab line(s) that YasT2 generated. Further, still on the client, do you know how to extract the relevant mount entries from /proc/mounts ? Then, on the server, can you provide your exports table? To sum up: Overall, it looks to me like the problem you're encountering is more-or-less what I'd expect to see when an NFS server goes offline. The clients will wait forever until the NFS server comes back online. -- 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