From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Mike Black" <mblack@csihq.com>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.8 NFS Problems
Date: Sat, 8 Sep 2001 12:53:27 +0200 [thread overview]
Message-ID: <15257.63655.764646.844202@charged.uio.no> (raw)
In-Reply-To: <04c301c137b4$34604590$e1de11cc@csihq.com>
In-Reply-To: <024f01c13601$c763d3c0$e1de11cc@csihq.com> <shsae07md9d.fsf@charged.uio.no> <033a01c1379e$e3514880$e1de11cc@csihq.com> <15256.56528.460569.700469@charged.uio.no> <04c301c137b4$34604590$e1de11cc@csihq.com>
>>>>> " " == 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
next prev parent reply other threads:[~2001-09-08 10:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-05 11:56 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 [this message]
2001-09-08 11:53 ` Mike Black
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=15257.63655.764646.844202@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=mblack@csihq.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®