public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Roger Heflin" <rheflin@atipa.com>
To: "'David Sanchez'" <david.sanchez@lexbox.fr>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Corrupted file on a copy
Date: Wed, 14 Sep 2005 11:41:50 -0500	[thread overview]
Message-ID: <EXCHG2003Rf3sllNY3000000791@EXCHG2003.microtech-ks.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0509141033580.17510@chaos.analogic.com>

 

> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org 
> [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of 
> linux-os (Dick Johnson)
> Sent: Wednesday, September 14, 2005 9:37 AM
> To: David Sanchez
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: Corrupted file on a copy
> 
> 
> On Wed, 14 Sep 2005, 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).
> > Does somebody have a same behaviour?
> >
> > Thanks,
> > David
> >
> 
> Use `cmp` to compare the two files. You could have discovered 
> a bug in your checksum utility, you need to isolate it to the 
> file-system. FYI, I have never seen a copy of a file, 
> including the image of an entire DVD (saved to clone 
> another), that was not properly identical.
> 

I have seen 2 similar issues.   Both where bad hardware of completely
different configurations (nothing at all in common, and completely
different machines).

Both would corrupt data on a read (we never found a corrupted
write).   One had a MTBF of 3 GB, and the other about 5GB, and if
you say made 200 50mb files (or however many you need to bust your
disk cache) , and do a checksum on all of them, the
checksum will be wrong on 1 or 2 of them each pass, and each pass
different files will be wrong (once you get all of the original
ones right on disk).  

Both were fixed by replacing the proper piece of hardware by a replacement
card, or by slowing down the pci bus one step to something that did not get
corruption.   In the second case both the card and the motherboard 
were rated for the speed that was getting corruption, and this problem
was duplicated with 2 different mb's of the same kind and 3 different 
pci cards, 1 of them being a completely different companies PCI card that
also
did not like the motherboard, but locked up linux rather than corrupted
data.

                           Roger


  reply	other threads:[~2005-09-14 16:37 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 [this message]
2005-09-14 16:28 ` Bill Davidsen
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=EXCHG2003Rf3sllNY3000000791@EXCHG2003.microtech-ks.com \
    --to=rheflin@atipa.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox