You should probably double check your hardware. I once had a similar error where every ~2,000,000,000th double word on the tape was corrupted. It turned out to be a bad mainboard (asus a7v133 pci problem). Run amverify regulary for a while, gzip will report these kind of errors (crc error).
Greetings, Moritz > You are right, but I have realized that many tapes have the same (let > instead lev) error or a gzip "corrupted data format" and never a tape header > error. I tested the drive with tar (1.13.17, 1.13.19 and 1.13.25) cpio and > dd (on old and new tapes) and it seems to work properly. > Could the problem be an exausted 6 tape set ? Why dumps terminate without > any I/O error? > Now, having changed some tapes, upgraded tar to 1.13.25 and gzip to 1.3.2 > (it was a thing that I already had to do), amrestoring tapes seems to work, > but I'm not sure of the problem. > [...]
