If you bunzip each of the individual recovery files generated by
bzip2recover, do they each decompress to exactly 921600 bytes?
Christian Hammers wrote:
So..
Alternative 1 "creating a .tar.bz2 that recovers to correct .tar files":
bzip2 by default and in this case explicitly specified is 900kb (Option
"-9"). So I created my test tar file with "--blocking-factor=1800" (and
with 900, did not make any difference).
Still, after I run bzip2recover, the first recovered block after the
corrupted one starts with 158065 junk bytes.
Alternative 2 "recovering a .tar.bz2 and let tar extract what's left":
That does not work, too, as is unable to skip those 158kb byte of
junk and then continue to recover the rest of the 250MB of data.
If, for performance reasons searching beyond the first e.g. 1kb is not
done there should be a corresponding option.
To my surprising tar's direct competitor cpio was able to restore the
broken *tar* file e.g. did exactly what I wanted :-)
"cpio -F part2.tar -i --no-absolute-filenames --make-directories -v"
Any more ideas what should be the "documented" way of dealing with compressed
tar archives?
bye,
_______________________________________________
Bug-tar mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-tar
