From: "Mike Black" <mblack@csihq.com>
To: <trond.myklebust@fys.uio.no>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.8 NFS Problems
Date: Sat, 8 Sep 2001 07:53:36 -0400 [thread overview]
Message-ID: <022001c1385c$e536b900$b6562341@cfl.rr.com> (raw)
In-Reply-To: LINKIFYABIACeeDGbdbGFDcDefEcACEDGfabdJacCHAHbDJLINKIFYFaACcBDIDGFEfbAeJFGJGaAFAHaddFbFEGCeabIJLINKIFYcHdJbAdfAJCHDdfEeeaJaFHfHJcbHDaBHJDAdEJCLINKIFYfcCEffABHcGJaaBIAHGCCGeBcdIfFcfIEBbEfCCeLINKIFYcHbIdJDDffGGFfaeecGfIIJfBHJHDeHAFecICGJd <15257.63655.764646.844202@charged.uio.no>
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/
next prev parent reply other threads:[~2001-09-08 11:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-05 11:56 2.4.8 NFS Problems Mike Black
2001-09-07 11:49 ` Trond Myklebust
2001-09-07 12:05 ` Peter T. Breuer
2001-09-07 12:27 ` Trond Myklebust
2001-09-07 12:36 ` Trond Myklebust
2001-09-07 13:13 ` Mike Black
2001-09-07 14:42 ` Trond Myklebust
2001-09-07 15:46 ` Mike Black
2001-09-08 10:53 ` Trond Myklebust
2001-09-08 11:53 ` Mike Black [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-20 9:44 Steffen Persvold
2001-12-20 11:10 ` Trond Myklebust
2001-12-20 14:40 ` Steffen Persvold
2001-12-20 20:27 ` Trond Myklebust
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='022001c1385c$e536b900$b6562341@cfl.rr.com' \
--to=mblack@csihq.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.