From: Dave Jones <davej@codemonkey.org.uk>
To: Daniel Pittman <daniel@rimspace.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux <-> Linux NFS issues.
Date: Fri, 21 Mar 2003 12:32:14 +0000 [thread overview]
Message-ID: <20030321123214.GB6664@suse.de> (raw)
In-Reply-To: <87isudm2ee.fsf@enki.rimspace.net>
On Fri, Mar 21, 2003 at 09:37:13PM +1100, Daniel Pittman wrote:
> The client machine reports, in dmesg:
> NFS: server cheating in read reply: count 4096 > recvd 1000
> The 'count' value is occasionally higher, but not often, and the 'recvd'
> never seems to differ from 1000.
When I was last seeing this, there was also a lot of 'crap' packets
on the wire, with bogus header lengths etc (some of which were so
malformed they broke ethereal).
I've not retried any NFS tests since 2.5.60, sounds like the problem
is still there, so I'll do some more investigation soon.
Dave
next prev parent reply other threads:[~2003-03-21 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-21 10:37 Linux <-> Linux NFS issues Daniel Pittman
2003-03-21 12:32 ` Dave Jones [this message]
2003-03-21 12:52 ` Trond Myklebust
2003-03-21 12:57 ` Dave Jones
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=20030321123214.GB6664@suse.de \
--to=davej@codemonkey.org.uk \
--cc=daniel@rimspace.net \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox