From: Craig Tierney <ctierney@hpti.com>
To: Nathan Scott <nathans@sgi.com>
Cc: Andy <genanr@emsphone.com>,
cattelan@sgi.com, linux-kernel@vger.kernel.org,
linux-xfs@oss.sgi.com
Subject: Re: NFS corruption (duplicated data)
Date: Tue, 08 Jun 2004 23:19:29 -0600 [thread overview]
Message-ID: <1086758368.3004.312.camel@localhost.localdomain> (raw)
In-Reply-To: <20040609095109.E1200131@wobbly.melbourne.sgi.com>
On Tue, 2004-06-08 at 17:51, Nathan Scott wrote:
> Hi Andy,
>
> Be good to try this with files served from ext2/3 as well,
> to try isolate it to XFS/NFS. We have a known issue thats
> possibly related to this in XFS - Russell, does this sound
> like that problem you've been looking at?
>
> If you have a simple test case to reproduce it (we have an
> extremely complex test case to reproduce that other issue,
> but from your description I'm not sure its the same), that
> would be very helpful Andy.
>
> thanks.
>
> On Tue, Jun 08, 2004 at 10:44:22AM -0500, Andy wrote:
> > 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
> >
Are you performing other IO on the NFS system while this copy is
occuring? Are you copying the same file over and over to try and
cause this problem?
Is it possible to zero all or as much disk as possible? If you are
copying the same file over and over, you might be seeing old data on
the disk and not necessarily seeing the filesystem putting the data in
the wrong place. This might help isolate the problem to the one Russell
is working on vs. a different problem.
Craig
prev parent reply other threads:[~2004-06-09 5:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 15:44 NFS corruption (duplicated data) Andy
2004-06-08 15:57 ` Trond Myklebust
2004-06-08 23:51 ` Nathan Scott
2004-06-09 2:12 ` Russell Cattelan
2004-06-09 5:19 ` Craig Tierney [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=1086758368.3004.312.camel@localhost.localdomain \
--to=ctierney@hpti.com \
--cc=cattelan@sgi.com \
--cc=genanr@emsphone.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=nathans@sgi.com \
/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.