http://bugzilla.novell.com/show_bug.cgi?id=500855
User sjayaraman@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=500855#c4
Suresh Jayaraman changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #4 from Suresh Jayaraman 2009-05-12 00:24:11 MDT ---
Thanks for the bug report and helping to isolate the problem.
If the 'soft' mount option is given, then -EIO is an expected result in some
cases of high load and busy network. If the problem never occurs when you use
hard, then I would think the behavior is expected. With the 'soft' mount option
the client fails after 'retrans' times retransmission and some of the errors
you mentioned in Comment #2 perhaps is the result of this option.
To quote the man page:
<snip>
soft / hard - Determines the recovery behavior of the NFS client after an NFS
request times out. If neither option is specified (or if the hard option is
specified), NFS requests are retried indefinitely. If the soft option is
specified, then the NFS client fails an NFS request after retrans
retransmissions have been sent, causing the NFS client to return an error to
the calling application.
NB: A so-called "soft" timeout can cause silent data corruption in certain
cases. As such, use the soft option only when client responsiveness is more
important than data integrity. Using NFS over TCP or increasing the value of
the retrans option may miti-gate some of the risks of using the soft option.
</snip>
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.