Greg Oster

You're most welcome! Thanks for coming up with a small test case -- I switched from 'dump' to 'restic' for backups at about the same time that I reported the issue, and so havn't had the need to chase this problem further. Later... Greg Oster

These changes are necessary, but not sufficient. A multi-tape dump looks like it is corrupting a file that spans two tapes. The error seen is: Incorrect block for <filename> at 11432470600 blocks Incorrect block for <filename> at 11432470601 blocks ... Incorrect block for <filename> at 11432470790 blocks Incorrect block for <filename> at 11432470791 blocks</filename></filename></filename></filename> When the 16TB restore finishes I'll know if this is the only file that is corrupt. [UPDATE: 16TB restore...

These changes are necessary, but not sufficient. A multi-tape dump looks like it is corrupting a file that spans two tapes. The error seen is: Incorrect block for <filename> at 11432470600 blocks Incorrect block for <filename> at 11432470601 blocks ... Incorrect block for <filename> at 11432470790 blocks Incorrect block for <filename> at 11432470791 blocks</filename></filename></filename></filename> When the 16TB restore finishes I'll know if this is the only file that is corrupt. I suspect that...

These changes are necessary, but not sufficient. A multi-tape dump looks like it is corrupting a file that spans two tapes. The error seen is: Incorrect block for <filename> at 11432470600 blocks Incorrect block for <filename> at 11432470601 blocks ... Incorrect block for <filename> at 11432470790 blocks Incorrect block for <filename> at 11432470791 blocks</filename></filename></filename></filename> When the 16TB restore finishes I'll know if this is the only file that is corrupt. I suspect that...

8.5TB of data successfully dumped/restored with the submitted patches in use. The dump/restore of this data set has 1000's of validation errors without the patches. Later... Greg Oster

Attached is a small diff to fix the percentages. Later... Greg Oster

My math here might be wrong... if 4294967296 is the maximum logical block address, then the corruption wouldn't be seen until LBAs of over that value.. I.e. for a block size of 4K, that would mean on filesystems larger than 16TB... which would help explain why this hasn't been reported before. Later... Greg Oster

corrupted dumps of 2TB+ filesystems....