From: Jamie Lokier <jamie@shareable.org>
To: Thomas Lenherr <thomas@lenherr.name>
Cc: Sonny Rao <sonny@burdell.org>, linux-fsdevel@vger.kernel.org
Subject: Re: PROBLEM: network filesystems corrupts files
Date: Sun, 24 Oct 2004 00:29:21 +0100 [thread overview]
Message-ID: <20041023232921.GA4340@mail.shareable.org> (raw)
In-Reply-To: <417AC932.104@lenherr.name>
I had a similar problem on a new x86 board recently, with 2.6.81
kernels, 2.4.20-31.9 kernels (Red Hat 9), and NFS, and memtest86
showed no erors.
It took a few days to discover that my problem was a hardware IDE
problem, and not a network problem. Bit errors appeared when I copied
remote files onto the local disk and then ran md5sum on them. When
the files were large enough, bit errors silently introduced by the IDE
interface resulted in MD5 mismatches.
The answer on this board case was to disable IDE DMA.
-- Jamie
prev parent reply other threads:[~2004-10-23 23:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-23 13:39 PROBLEM: network filesystems corrupts files Thomas Lenherr
2004-10-23 18:14 ` Sonny Rao
2004-10-23 18:43 ` Thomas Lenherr
2004-10-23 19:55 ` Thomas Lenherr
2004-10-23 20:48 ` Sonny Rao
2004-10-23 21:12 ` Thomas Lenherr
2004-10-23 23:29 ` Jamie Lokier [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=20041023232921.GA4340@mail.shareable.org \
--to=jamie@shareable.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sonny@burdell.org \
--cc=thomas@lenherr.name \
/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;
as well as URLs for NNTP newsgroup(s).