Subject: Re: corruption on compression, or bitrot?
To: Ben Collver <collver@peak.org>
From: The Grey Wolf <greywolf@starwolf.com>
List: current-users
Date: 09/09/2004 17:44:42
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Thus spake Ben Collver ("BC> ") sometime Today...
BC> Possibly a memory error as well. If this is i386, you might want to try
BC> sysutils/memtest86.
I don't think so:
/* pseudo-code */
for (;*file; ++file) {
finished=0;
if (!finished) {
compresscat(file, ".gz");
uncompresscat(zfile, "/dev/null") &&
finished++;
}
}
i.e. if the uncompress fails, go back and re-compress it and test it
again until we get it right.
And I don't think it's the drive, since I've tried it with a different
drive.
Once a gzipped file has gone bad, it remains so.
The checksum on the file actually *changes* at SOME point ->after<-
the file has been closed and some other file is being written, somewhere
down the line.
I'm more and more starting to suspect the filesystem, but I can't
confirm that until I get -current running on my sparc and test it
there.
BC> Cheers,
BC>
BC> Ben
--*greywolf;
- --
Have a Nice Day. (All taxes are the sole responsibility of the winner.)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)
iD8DBQFBQPj+DOGizqAnVRERAmopAKCbtKuFrr03zE98X3BFR6h8hNz2rACfSyuX
FoGd1KkoWy51c6H8tVPl/yc=
=32nJ
-----END PGP SIGNATURE-----