Bradley writes: > Running into a problem with my larger machines doing backups. 90% of > the time, the backup ends with the following message: > > backup failed (Tar exited with error 256 () status) > > I believe I read somewhere that it was due to a file changing during > backup, probably in combination with the latency introducted in backup > across the network. > > The reason I went with tar in the first place is that I read > that rsync consumes more memory the larger the file list is, > and this box has 256MB of RAM. > > My question at this point is the best approach to fixing this > problem. I have been running backuppc since the beginning of the > year, so I have at least 2 fulls and a weeks worth of incrementals, > so, at least in theory, the number of files being rsynced should > not be overly large. So should I convert my "problem children" to > rsync, or should I convert everything over to rsync? Or is there a > workaround for tar?
What version of tar are you using? Torsten reported that the newest version has changed the exit status in the case of certain relatively benign warnings that are therefore considerd fatal by BackupPC. Could you also look through the XferLOG file and confirm that it is this same warning that tar is reporting? I still need to fix this issue for 3.x. Craig ---------- Forwarded message ---------- To: [email protected] From: Torsten Sadowski <[EMAIL PROTECTED]> Date: Fri, 1 Dec 2006 13:55:15 +0100 Subj: [BackupPC-users] /bin/tar: ./totty: file changed as we read it 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) ---------- Forwarded message ---------- To: [email protected] From: Torsten Sadowski <[EMAIL PROTECTED]> Date: Tue, 5 Dec 2006 10:35:51 +0100 Subj: Re: [BackupPC-users] /bin/tar: ./totty: file changed as we read it 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/
