Eero Ahonen wrote:
> 
> I'm still pretty sure you'll need the whole file in case of bzip2. But

Now I'm even more sure, I tested ;). I drained 10M of random data to a
file, compressed it, had 11M file :), took first 10M of it and tried to
uncompress it.

aero@groath ~ $ dd if=/dev/urandom of=temp/testi bs=1M count=10
cd temp
ls10+0 records in
10+0 records out
10485760 bytes (10 MB) copied, 2.41001 s, 4.4 MB/s
aero@groath ~ $ cd temp
aero@groath ~/temp $ ls -lah|grep testi
-rw-r--r--  1 aero aero  10M Jan  5 21:16 testi
aero@groath ~/temp $ bzip2 testi
aero@groath ~/temp $ ls -lah|grep testi
-rw-r--r--  1 aero aero  11M Jan  5 21:16 testi.bz2
aero@groath ~/temp $ dd if=testi.bz2 of=testi2.bz2 bs=1M count=10
10+0 records in
10+0 records out
10485760 bytes (10 MB) copied, 0.0284283 s, 369 MB/s
aero@groath ~/temp $ bunzip2 testi2.bz2

bunzip2: Compressed file ends unexpectedly;
        perhaps it is corrupted?  *Possible* reason follows.
bunzip2: No such file or directory
        Input file = testi2.bz2, output file = testi2

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.

bunzip2: Deleting output file testi2, if it exists.

-Aero

Post a reply to this message