> Hi Norman, > > Thank you for reporting this issue. > > I see in mondo-archive.log: > > [Main] libmondo-verify.c->verify_afioballs_on_CD#263: set = 219 > [Main] libmondo-verify.c->verify_an_afioball_from_CD#615: > Verifying /dtv2/tmp.mondo.25882/tmp.mondo.26014/cdrom/archives/219.afio.bz2 > [Main] libmondo-verify.c->verify_a_tarball#508: Verifying > fileset > '/dtv2/tmp.mondo.25882/tmp.mondo.26014/cdrom/archives/219.afio.bz2' > [Main] libmondo-verify.c->verify_a_tarball#541: > afio -r -P bzip2 > -Z /dtv2/tmp.mondo.25882/tmp.mondo.26014/cdrom/archives/219.afio.bz2 > >> /dtv2/tmp.mondo.25882/tmp.mondo.260 > $'/dtv2/tmp.mondo.25882/tmp.mondo.26014/cdrom/archives/219.afio.bz2' - > differences found > afio: / > > afio: / Input file = (stdin), output file = (stdout) > > afio: /usr/lib/libcdda_interface.so.0.9.8 > afio: / Data integrity error when decompressing. > > afio: /It is possible that the compressed file(s) have become corrupted. > > afio: /You can use the -tvv option to test integrity of such files. > > afio: /You can use the `bzip2recover' program to attempt to recover > > afio: /data from undamaged sections of corrupted files. > > and the same for set 348. > > Could you loop-mount the ISO image and test whether these files are in > fact corrupt by doing: > > bunzip -tvv 219.afio.bz2 > > and > > bunzip -tvv 348.afio.bz
Andree, I'm embarrassed to say that I'm not sure I saved the .iso file --- and even if I did, the hard drive with that .iso on it is now sitting in the basement of my house. > Other than that, the above log is from a mondoarchive run. Could you > send the log from the failed mondorestore run? All I have is the log file I sent you (with probably some later archive/restore runs as well). Where should I be looking for the mondorestore log? I apologize for sending in what may turn out to be a useless bug report. Next time I do a backup, if anything goes wrong I will be more careful to save evidence. (Though at present I'm a bit short of space for 4GB files.) I do have a gentle comment---the log files are quite difficult to read for those not already knowing how mondo works. It might be worth investing some effort trying to make them more perspecuous. One other thing you might find it helpful to know: during one of my other restore attempts, my filesystem ran out of inodes. In this case, mondo reports 'No space left on device', but of course df(1) reports lots of blocks available. It might be worth putting a note in mondo's documentation reminding people to check 'df -i'. Norman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
