From: Ondrej Zary <linux@rainbow-software.org>
To: David Sanchez <david.sanchez@lexbox.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Write file corruption - The next
Date: Fri, 07 Oct 2005 21:46:15 +0200 [thread overview]
Message-ID: <4346D087.3020505@rainbow-software.org> (raw)
In-Reply-To: <17AB476A04B7C842887E0EB1F268111E026FF7@xpserver.intra.lexbox.org>
David Sanchez wrote:
> Hi,
>
> When I copy big file around (500MB) then sometimes the copied file
> differs from the source!
>
> I try big copy on an AMD dbau1550 and on an EPIA Mini-ITX board using
> several Sata promise controllers (with DMA and without DMA) and using
> the IDE interface (with DMA and without DMA) and the problem still
> appears!!
>
> More I try busybox 1.0 and 1.01 with kernel 2.4 to 2.6.13 and the
> problem still appears... memtest tool doesn't detect error...
Try GoldMemory - http://www.goldmemory.cz - it can sometimes detect a
memory error that memtest can't.
--
Ondrej Zary
prev parent reply other threads:[~2005-10-07 19:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 8:57 Write file corruption - The next David Sanchez
2005-10-07 19:46 ` Ondrej Zary [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=4346D087.3020505@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=david.sanchez@lexbox.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox