From: Andy <genanr@emsphone.com>
To: linux-kernel@vger.kernel.org
Subject: NFS corruption (duplicated data)
Date: Tue, 8 Jun 2004 10:44:22 -0500 [thread overview]
Message-ID: <20040608154422.GA3946@thumper2> (raw)
I really don't understand what could be causing this, but it happens on
several machine and at least on kernels 2.4.22, 2.4.25, 2.4.26.
NFS v3 : hard, udp, rsize=8192,wsize=8192
local filesystems are XFS
Trond, this is data corruption not dropped packets so the protocol
being UDP is not the problem.
Here is what is happening :
Copying a file of offsets from machine A to machine B over NFS and then
comparing the file on B with the file on A over NFS, the file on machine B
is corrupted in the following ways.
Usually, data earlier in the file will show up again later.
For example :
57344 bytes of data from 672190464-672247807 is also in positions
1449664512-1449721855
sometimes, data later in the file is dupped to a position before it
should be
53248 bytes of data from 1197158400-1197211647 is also in positions
1036660736-1036713983
Any ideas
Andy
next reply other threads:[~2004-06-08 15:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 15:44 Andy [this message]
2004-06-08 15:57 ` NFS corruption (duplicated data) Trond Myklebust
2004-06-08 23:51 ` Nathan Scott
2004-06-09 2:12 ` Russell Cattelan
2004-06-09 5:19 ` Craig Tierney
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=20040608154422.GA3946@thumper2 \
--to=genanr@emsphone.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.