-f option results in invalid index

[redneb]

When I create a tpxz archive as follows

$ pixz -9 -f 3 linux-3.7.4.tar linux-3.7.4.tpxz

then the resulting archive has a corrupt index:

$ pixz -x linux-3.7.4/README < linux-3.7.4.tpxz > /dev/null 
Index and archive differ as to next file: linux-3.7.4/README vs linux-3.7.4/

This seems to happen for all values of -f greater than 2. I've only tested this with the -9 compression level.

[vasi]

Thanks for the report. I'll try to look into it soon.

[vasi]

Ok, bug confirmed. I'm starting to work on it, but it involves some pretty grotty code, so no promises yet. It might have to wait for the next minor version. The specific problem is that the code that finds specific wanted files hasn't been properly updated to deal with blocks of data that are so huge we don't want to keep them in memory.

Some related huge-blocks problems that this helped me find, and that are fixed:

• Threads would sometimes get starved, causing a hang.
• Auto-detection of the file-index would fail.