From: Dave Jones <davej@codemonkey.org.uk>
To: CaT <cat@zip.com.au>
Cc: linux-kernel@vger.kernel.org, neilb@cse.unsw.edu.au
Subject: Re: 2.5->2.4 nfs corrupts
Date: Thu, 10 Apr 2003 02:44:17 +0100 [thread overview]
Message-ID: <20030410014417.GA3197@suse.de> (raw)
In-Reply-To: <20030410013349.GC467@zip.com.au>
On Thu, Apr 10, 2003 at 11:33:49AM +1000, CaT wrote:
> nfs server: 2.4.21-pre2
> nfs client: 2.5.67
Quite a few people (myself included) are seeing this.
>From the reports I've seen so far, it looks like it only
happens when the client is a faster box than the server.
In my case, I have a 2.8Ghz P4 as the client, hammering
a poor defenceless 1Ghz VIA C3.
This is probably worth creating a bugzilla entry for.
Dave
next prev parent reply other threads:[~2003-04-10 1:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-10 1:33 2.5->2.4 nfs corrupts CaT
2003-04-10 1:44 ` Dave Jones [this message]
2003-04-10 4:20 ` CaT
2003-04-10 7:50 ` Petition against EU software patents Giuliano Pochini
2003-04-10 8:20 ` 2.5->2.4 nfs corrupts Erik Hensema
2003-04-10 10:28 ` 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=20030410014417.GA3197@suse.de \
--to=davej@codemonkey.org.uk \
--cc=cat@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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