search

ckolivas / lrzip

Long Range Zip
http://lrzip.kolivas.org
GNU General Public License v2.0
618 stars 76 forks source link

error running lrunzip on large encrypted lrzip file #48

Closed GitBillW closed 8 years ago

GitBillW commented 8 years ago

My tests suggest that both of these conditions need to apply to produce this error:

Here's a test scenario with an 8GB input file: lrzip, then lrunzip the result. The output should be identical to the input , but it is short:

lrzip -e -f -v -o test8.lrz test8 && lrunzip -f -v -o test8.lrz.out test8.lrz
-rw-------  1 root   root 8589934592 2016/04/04 13:26:53 test8
-rw-------  1 root   root 3100380112 2016/04/04 17:39:10 test8.lrz
-rw-------  1 root   root 8413675520 2016/04/04 17:46:44 test8.lrz.out

No error messages are seen during lrzip, but "chunk_bytes <#> is invalid in runzip_chunk" is seen during lrunzip.

The same error can be seen with smaller input files if the lrzip -w flag is used to specify a smaller than default compression window size: eg "-w 1" makes the error show up with a 100MB input file.

I'm running on a 64-bit Debian Stable (Jessie) system with 12GB of RAM and an Intel Core i7-950 processor. I've tried both lrzip-0.616 (the current version on the Debian Stable repo) and lrzip-0.621 which I built myself from the source on https://github.com/ckolivas/lrzip/releases They both error in the same way.

Any idea what might be happening, and how I can investigate further?

ckolivas commented 8 years ago

That looks like a bad bug indeed. There's probably no need to investigate further unless you're planning on delving into the code as it's almost certainly a bug there. Alas I have no time to address this any time soon.

GitBillW commented 8 years ago

I'm in no hurry for a fix, as I'm working around the issue by using lrzip for compression and gpg for encryption. I recently changed from pxz to lrzip, which gives me better compression while at the same time being kinder to my processor: 8 cores of pxz get the CPU temperature uncomfortably close to the recommended maximum.

When you have the time, a fix would be nice.

ckolivas commented 8 years ago

Should be fixed in git now.

GitBillW commented 8 years ago

Thanks Con, it's working perfectly now.

Bill

On 09/06/16 06:01, Con Kolivas wrote:

Should be fixed in git now.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ckolivas/lrzip/issues/48#issuecomment-224800428, or mute the thread https://github.com/notifications/unsubscribe/ARaw7ux4vODWY9t1blLQsu22f-7GYy0bks5qJ54rgaJpZM4IC7Op.