Hi,
My investigation leads me to suspect the read operation.
I divide the CPU frequency by two and the problem no more occurred!
I carry on my investigation...
Thanks,
David SANCHEZ
LexBox :: The Digital Evidence
3, avenue Didier Daurat
31400 TOULOUSE / FRANCE
[email protected]
Tel : +33 (0)5 62 47 15 81
Fax : +33 (0)5 62 47 15 84
-----Message d'origine-----
De : [email protected] [mailto:[email protected]] De la part de Roger Heflin
Envoyé : mercredi 14 septembre 2005 18:46
À : David Sanchez
Cc : [email protected]
Objet : RE: Corrupted file on a copy
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of
> linux-os (Dick Johnson)
> Sent: Wednesday, September 14, 2005 9:37 AM
> To: David Sanchez
> Cc: [email protected]
> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |