All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: David Sanchez <david.sanchez@lexbox.fr>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Corrupted file on a copy
Date: Wed, 14 Sep 2005 12:28:25 -0400	[thread overview]
Message-ID: <43284FA9.3030507@tmr.com> (raw)
In-Reply-To: <17AB476A04B7C842887E0EB1F268111E026F9B@xpserver.intra.lexbox.org>

David Sanchez wrote:
> Hi,
> 
> I'm using the linux kernel 2.6.10 and busybox 1.0 on a AMD AU1550 board.
> 
> When I copy a big file (around 300M) within an ext2 filesystem (even on
> ext3 filesystem) then the output file is sometime "corrupted" (I mean
> that the source and the destination files are different and thus
> generate a different SHA1).

That's likely to be hardware. Have you tried memtest86 or similar? Are 
you overclocked, or running aggressive memory timing?

Similar kernel+bbox installs seem stable on other hardware.


-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me


  parent reply	other threads:[~2005-09-14 16:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-14 13:14 Corrupted file on a copy David Sanchez
2005-09-14 14:36 ` linux-os (Dick Johnson)
2005-09-14 16:41   ` Roger Heflin
2005-09-14 16:28 ` Bill Davidsen [this message]
2005-09-14 21:05 ` Chris Wedgwood
  -- strict thread matches above, loose matches on Subject: below --
2005-09-14 14:56 David Sanchez
2005-09-14 15:16 ` linux-os (Dick Johnson)
2005-09-15 10:01 David Sanchez

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=43284FA9.3030507@tmr.com \
    --to=davidsen@tmr.com \
    --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 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.