From: Nix <nix@esperi.demon.co.uk>
To: ultralinux@vger.kernel.org
Subject: Re: strange sparc64 -> i586 intermittent but reproducible NFS write errors to one and only one fs
Date: Mon, 03 Feb 2003 17:35:03 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-104429521920641@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-104300775807656@msgid-missing>
On Sun, 19 Jan 2003, Trond Myklebust said:
> It sounds rather strange that this particular patch should introduce
> an EIO, but here it is (fresh from BitKeeper)
... and indeed it doesn't.
The problem still exists in -pre9, but is very much rarer and harder to
replicate; I've sene it only half a dozen times in two weeks, in each
case during an ftp retrieval; I'm assuming there's something about the
write patterns used by ncftp (lots of few-KB appends, far apart in time)
that triggers it.
So it really is merely a timing change that has brought a pre-existing
problem into the light.
I'm going to try to come up with something that consistently reproduces
this as well, so I can track down the origins of this bug more
correctly.
--
2003-02-01: the day the STS died.
next prev parent reply other threads:[~2003-02-03 17:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-19 20:21 strange sparc64 -> i586 intermittent but reproducible NFS write errors to one and only one fs Nix
2003-01-19 21:00 ` Trond Myklebust
2003-01-20 6:01 ` strange sparc64 -> i586 intermittent but reproducible NFS write David S. Miller
2003-01-20 20:53 ` strange sparc64 -> i586 intermittent but reproducible NFS write errors to one and only one fs Nix
2003-02-03 17:35 ` Nix [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-09 22:56 Nix
2003-01-10 6:57 ` Denis Vlasenko
2003-01-19 20:21 ` Nix
2003-01-19 21:00 ` Trond Myklebust
2003-01-20 6:38 ` David S. Miller
2003-01-20 20:53 ` Nix
2003-02-03 17:35 ` Nix
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=marc-linux-ultrasparc-104429521920641@msgid-missing \
--to=nix@esperi.demon.co.uk \
--cc=ultralinux@vger.kernel.org \
/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.