linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: CaT <cat@zip.com.au>
To: Dave Jones <davej@codemonkey.org.uk>,
	linux-kernel@vger.kernel.org, neilb@cse.unsw.edu.au
Subject: Re: 2.5->2.4 nfs corrupts
Date: Thu, 10 Apr 2003 14:20:15 +1000	[thread overview]
Message-ID: <20030410042015.GD467@zip.com.au> (raw)
In-Reply-To: <20030410014417.GA3197@suse.de>

On Thu, Apr 10, 2003 at 02:44:17AM +0100, Dave Jones wrote:
> 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 the case here also: a p3 700 hammering a k6 300.

> This is probably worth creating a bugzilla entry for.

Would this be something I'd do or someone else?

-- 
Martin's distress was in contrast to the bitter satisfaction of some
of his fellow marines as they surveyed the scene. "The Iraqis are sick
people and we are the chemotherapy," said Corporal Ryan Dupre. "I am
starting to hate this country. Wait till I get hold of a friggin' Iraqi.
No, I won't get hold of one. I'll just kill him."
	- http://www.informationclearinghouse.info/article2479.htm

  reply	other threads:[~2003-04-10  4:10 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
2003-04-10  4:20   ` CaT [this message]
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=20030410042015.GD467@zip.com.au \
    --to=cat@zip.com.au \
    --cc=davej@codemonkey.org.uk \
    --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;
as well as URLs for NNTP newsgroup(s).