From: Kenneth Johansson <ken@kenjo.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: NFS corruption on 2.6.11.7
Date: Wed, 25 May 2005 22:13:27 +0200 [thread overview]
Message-ID: <1117052007.9884.10.camel@tiger> (raw)
In-Reply-To: <1116936088.10707.39.camel@lade.trondhjem.org>
[-- Attachment #1: Type: text/plain, Size: 690 bytes --]
On Tue, 2005-05-24 at 08:01 -0400, Trond Myklebust wrote:
> Again, please could you give us more details on how you are doing these
> tests: what hardware (i.e. what NIC, switch, server, memory,...), lsmod
> output, (and ditto for the server).
After changing the mount option to use tcp instead of udp I have now
read several gigabytes without a single error.
Is there some fundamental difference in how nfs over upd and tcp is
handled regarding the packet contents like tcp using the tcp checksum
and udp not using the udp checksum or something like that?
Are there any counters for checksum errors in udp and tcp that can be
read ?? I faild to spot anything in /proc.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-05-25 20:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-23 22:47 NFS corruption on 2.6.11.7 Kenneth Johansson
2005-05-24 0:35 ` Trond Myklebust
2005-05-24 1:04 ` Trond Myklebust
2005-05-24 10:15 ` Kenneth Johansson
2005-05-24 12:01 ` Trond Myklebust
2005-05-24 14:58 ` Kenneth Johansson
2005-05-25 20:13 ` Kenneth Johansson [this message]
[not found] ` <20050525.131616.59655785.davem@davemloft.net>
2005-05-25 20:34 ` Kenneth Johansson
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=1117052007.9884.10.camel@tiger \
--to=ken@kenjo.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