Hello!
> I just write a series of uncompressed tarballs, created from tarring up
> filesystems. Now that I've got copies of everything on the second
> server, it was easiest to create the tarballs there. Then I mounted them
> over nfs and copied them to the old server ready to write to tape from
> the staging directory. After the problems, I decided it was best to
> take md5sums after copying : two differed (out of about 10 copied).
> Repeated, this time copying with scp : one of the two was ok, but the
> other had to be copied twice before I got the correct md5.
Huh! That just sounds like the problems I had with my medium-old box:
Copying files from and to that machine produced corrupt files (md5sum
different). I traced that back to a flawed chipset (VIA KT133 of
course..). It seems that a BIOS update somewhat eased the trouble, at
least since then copying 'works'.
It didn't matter what protocol was used to transfer the files (okay, I
only tried SMB and FTP) and the problem occured randomly on larger
files.
Have you tried to look for perhaps available BIOS updates for your
boards, or know problems with them? In my case it was the
UDMA-controller part that was/is broken, and I still don't trust this
system as it keeps mis-burning DVDs every now and then.
Cheers,
Steffen
--
If something is so complicated that you can't explain it in 10 seconds,
then it's probably not worth knowing anyway. -- Calvin
pgpRcQxkJSAKy.pgp
Description: PGP signature
-- http://linuxfromscratch.org/mailman/listinfo/lfs-chat FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
