Antonio Diaz Diaz wrote:
The diagnostic above does not come from minilzip.c, but from line 476 in function 'cworker' in create_lz.cc. It happens when the file being read and archived ends before its expected size. The reading is performed by the function 'readblock', which reads in a loop until the file ends or until something fails. So it is probable that the file 'dir/foo' has indeed some issue.
Tarlz reads and compresses files in parallel (multithreaded) when creating a compressed archive. Therefore the problem may be with parallel accesses to the file system. This could explain why it worked when you archived 'dir/foo' alone. How many processors are in your machine?
Best regards, Antonio.
