I found the reason and a (for now) quick solution. The Reason first (from: http://cvs.savannah.gnu.org/viewcvs/tar/NEWS?rev=1.125&root=tar&view=auto):
GNU tar NEWS - User visible changes. Please send GNU tar bug reports to <[email protected]> version 1.16 - Sergey Poznyakoff, 2006-10-21 * After creating an archive, tar exits with code 1 if some files were changed while being read. Previous versions exited with code 2 (fatal error), and only if some files were truncated while being archived. The quick solution was to download tar-1.15.1, build and use it. Does 3.0.0 work with tar 1.16? Torsten Am Freitag, 1. Dezember 2006 13:55 schrieb Torsten Sadowski: > Hi, > > the new tar seems to be a bit more nervous than the old one. One Problem > could be solved with LANG=C but another point are probably changes in the > backed up filesystem. Is there a possibility to ignore this error? > > Cheers, Torsten > > /bin/tar: ./totty: file changed as we read it > [ skipped 1 lines ] > Tar exited with error 256 () status > [ skipped 46 lines ] > tarExtract: Done: 0 errors, 1557378 filesExist, 63760417431 sizeExist, > 45188423124 sizeExistComp, 1615232 filesTotal, 63767351947 sizeTotal > Got fatal error during xfer (Tar exited with error 256 () status) > Backup aborted (Tar exited with error 256 () status) > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ BackupPC-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
