On 2012-06-07 03:20:37 +0200, Vincent Lefevre wrote:
> Now, the way bunzip2 does integrity checking when decompressing is
> poorly documented: does bunzip2 guarantee that every byte from the
> stream is correct (e.g. integrity checking is done chunk by chunk,
> and a chunk is output only once CRC checking has been done on it)
> or does one need to wait for the decompression of the full file to
> detect a possible integrity error?
>
> If this is the latter, then the problem could come from the file
> server, because my own MD5 checking has detected the problem before
> the file has entirely been decompressed. In such a case, I would
> need to modify my script for better information on the failure.
I think I have the answer. My test in loop has just given:
This is ckdump 50073 2012-03-01 14:12:19
Reading the md5 file...
Starting bunzip2 on mpfr-0-8207.bz2 ...
Checking the dump file...
Revision 6952
bunzip2: Data integrity error when decompressing.
Input file = mpfr-0-8207.bz2, output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
ckdump: bunzip2 died (exit value: 2)
i.e. I got the integrity error in the middle of the stream.
Other failing tests:
This is ckdump 50073 2012-03-01 14:12:19
Reading the md5 file...
Starting bunzip2 on mpfr-0-8207.bz2 ...
Checking the dump file...
ckdump: bad MD5 for revision 7899 (output to ckdump.r7899)
This is ckdump 50073 2012-03-01 14:12:19
Reading the md5 file...
Starting bunzip2 on mpfr-0-8207.bz2 ...
Checking the dump file...
Revision 5654
bunzip2: Data integrity error when decompressing.
Input file = mpfr-0-8207.bz2, output file = (stdout)
[...]
This is ckdump 50073 2012-03-01 14:12:19
Reading the md5 file...
Starting bunzip2 on mpfr-0-8207.bz2 ...
Checking the dump file...
Revision 7875
bunzip2: Data integrity error when decompressing.
Input file = mpfr-0-8207.bz2, output file = (stdout)
[...]
This is ckdump 50073 2012-03-01 14:12:19
Reading the md5 file...
Starting bunzip2 on mpfr-0-8207.bz2 ...
Checking the dump file...
ckdump: bad MD5 for revision 7588 (output to ckdump.r7588)
The fact I do not always get an integrity error probably means
that the problem doesn't come from the file server.
This was still on the same machine (the other two are fine).
Possibly a hardware problem, unless there's something else
special with this machine.
--
Vincent Lefèvre <vinc...@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
