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.
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
> 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
> Any ideas
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/