Messages in this thread |  | | From | "Mike Black" <> | Subject | Re: 2.4.8 NFS Problems | Date | Sat, 8 Sep 2001 07:53:36 -0400 |
| |
Did some more testing this A.M.
Soft Mount: Took me several tries -- had to run a tiobench on the server side to make for some I/O contention. Was able to get EIO error (since this is Sat the system was pretty idle). Hard Mount: Unable to reproduce even though 10 second timeouts could be seen. Soft Mount (retrans=5) Unable to reproduce
Could be the interaction with ext3 where I/O gets bound up a while. Just long enough to trigger the timeouts for a soft mount. ----- Original Message ----- From: "Trond Myklebust" <trond.myklebust@fys.uio.no> To: "Mike Black" <mblack@csihq.com> Cc: "linux-kernel" <linux-kernel@vger.kernel.org> Sent: Saturday, September 08, 2001 6:53 AM Subject: Re: 2.4.8 NFS Problems
> >>>>> " " == Mike Black <mblack@csihq.com> writes: > > > The file is being copied from yeti to picard. Last packet seen > > is picard telling yeti "OK" after the commit. If soft timeouts > > were occurring shouldn't we be seeing packets from yeti again > > with no response from picard? > > You are assuming that the last packet seen is the one that corresponds > to your read. In doing so, you are neglecting the fact that these are > asynchronous reads, and that file readahead can muddle the waters for > you. > > Look, this is getting us nowhere. The bottom line is: if you are able > to reproduce the EIO on hard mounts it is a bug, and I'll be happy to > help you trace it. If it is occuring only on soft mounts, it is user > error... > > Cheers, > Trond > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |