From: Paul Mundt <lethal@linux-sh.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: NFS weirdness in 2.6.0-test1
Date: Tue, 29 Jul 2003 21:57:56 -0400 [thread overview]
Message-ID: <20030730015756.GA2137@linux-sh.org> (raw)
In-Reply-To: <16166.46256.737464.27553@charged.uio.no>
[-- Attachment #1: Type: text/plain, Size: 447 bytes --]
On Tue, Jul 29, 2003 at 07:53:52PM +0200, Trond Myklebust wrote:
> > NFS: server cheating in read reply: count 1526 > recvd 1000
> > NFS: server cheating in read reply: count 4096 > recvd 1000
> > NFS: server cheating in read reply: count 1583 > recvd 1000
>
> Does the following patch fix it?
>
Yes, this seems to work fine. I've been running this for awhile now
under relative load, and haven't seen any data corruption.
Thanks!
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2003-07-30 1:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030725151127.GA2947@linux-sh.org>
[not found] ` <16161.25923.623651.618044@charged.uio.no>
[not found] ` <20030726015007.GA18944@linux-sh.org>
2003-07-28 19:48 ` NFS weirdness in 2.6.0-test1 Trond Myklebust
2003-07-29 17:53 ` Trond Myklebust
2003-07-30 1:57 ` Paul Mundt [this message]
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=20030730015756.GA2137@linux-sh.org \
--to=lethal@linux-sh.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox