https://bugzilla.novell.com/show_bug.cgi?id=743969
https://bugzilla.novell.com/show_bug.cgi?id=743969#c1
Ned Ulbricht changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nedu@netscape.net
--- Comment #1 from Ned Ulbricht 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.
