>
> > Of course, you're right :) (although pigz failed only in 2 files out of
> > several thousands).
>
> oh well, I was wondering about that. I've yet to see such a file (and
> probably never will, because I disabled pool compression for good and
> now use btrfs' lzop filesystem-based compression)
Hi,
On 27.11.18 13:40, Guillermo Rozas wrote:
Pigz doesn't correctly support BackupPC compressed files, although
it will in some cases. The reported error is likely the problem.
Please use BackupPC_zcat instead and report back.
Of course, you're right :) (although pigz failed on
>
> Pigz doesn't correctly support BackupPC compressed files, although it will
> in some cases. The reported error is likely the problem. Please use
> BackupPC_zcat instead and report back.
>
Of course, you're right :) (although pigz failed only in 2 files out of
several thousands).
BackupPC_zc
Guillermo,
Actually, I'm still unsure if there is a problem with the files themselves
> or with the decompression, as pigz complains that "trailing junk was
> ignored" on both files. Any idea why could be that?
Pigz doesn't correctly support BackupPC compressed files, although it will
in some ca
Hi,
following the advice from Alex [1] I successfully created a script to check
the cpool on the server for checksum errors. So far I've found 2 files
whose name do not match their checksum. Is there a simple way to find to
which paths correspond those files given their MD5 digest?
Actually, I'm