Closed pete4abw closed 1 year ago
Cannot reproduce issue with lrzip-next. I compressed, then tested, the same large file I reproduced the issue with on standard lrzip, and everything appears to work.
log: lrzip-next-log.txt
(originally I had the log inline but it made a giant long comment
Cannot reproduce issue with lrzip-next. I compressed, then tested, the same large file I reproduced the issue with on standard lrzip, and everything appears to work.
log: lrzip-next-log.txt
(originally I had the log inline but it made a giant long comment
Yes, it was a long reply, @ArrayBolt3 :-)! But a useful one. I am sure it won't make a difference, BUT may I ask that you do try and decompress the file now? I know it's a pain and 2 hrs+, but maybe you can do overnight? Use -O dirname
to redirect the output to another directory so it does not affect your compressed file.
e.g. lrzip-next -vvd -O /tmp Compaq_Presario_CQ57_Factory_Reset_Disk.img
lrzip-next, aside from being a significant enhancement to lrzip, also has new compression methods added, including bzip3 and zstd and many new options. I hope you'll give it a try and help with feedback.
Thank you again for your support and helping review this issue.
It's no problem at all, since lrzip uses a high nice value. I can just leave it on in the background :)
Decompression is underway now. Thanks for the work you do making this software!
Decompression was successful, and cmp
indicates that the file was accurately decompressed.
Decompression was successful, and
cmp
indicates that the file was accurately decompressed.
Well, thank you for your effort. I can only assume that a) the SDK used in lrzip-next for zpaq (7.15) solved the issue, or b) other enhancements I have made since I forked off in 2019 solved the issue. I have made numerous enhancements. And sadly, the maintainer of zpaq, Matt Mahoney has retired and no enhancements have been made since 2016.
I'm going to close this since for lrzip-next, this is not an issue. I can't help with lrzip since it's so out of date with current SDKs of both lzma and zpaq.
This issue, from lrzip, needs more info and some help to review.
The major, important difference wrt this reported bug, is that
lrzip-next
uses a much newer SDK for zpaq.Anyone who investigates, please do not use any shortcuts. Just use
lrzip-next -vv [options]
and not uselrzncat
,lrznunzip
. Also for testing purposes, don't decompress. Uselrzip-next -vvt file
. It is important to use-vv
and capture all output.@ArrayBolt3 , since you are the latest reporter, try your issue here.
Thank you.