Hi,
Thomas G?nther wrote on 03.07.2007 at 10:59:10 [Re: [BackupPC-users] problems
during/after backup]:
> >> I am using BackupPC 2.1.2 on a Debian (Etch) server. [...]
>
> But now I have got (same job, but fewer directories and files):
>
> [...]
> Backup aborted (Tar exited with error 256 () status)
> dump failed: Tar exited with error 256 () status
> [...]
> It seems to be a problem of "tar", isn't it?
that's a change in tar's exit code in version 1.16 which signals the fact that
files changed while tar was reading them. This is non-fatal and is ignored in
BackupPC 3.0.0. If you don't want to upgrade, you can patch 2.1.2:
--- lib/BackupPC/Xfer/Tar.pm Sun Jan 8 23:25:54 2006
+++ /tmp/Tar.pm Tue Jul 3 11:10:04 2007
@@ -198,7 +198,12 @@
my $mesg;
if ( sysread($t->{pipeTar}, $mesg, 8192) <= 0 ) {
vec($$FDreadRef, fileno($t->{pipeTar}), 1) = 0;
- if ( !close($t->{pipeTar}) ) {
+ if ( !close($t->{pipeTar}) && $! != 256 ) {
+ #
+ # Tar 1.16 uses exit status 1 (256) when some files
+ # changed during archive creation. We allow this
+ # as a benign error and consider the archive ok
+ #
$t->{tarOut} .= "Tar exited with error $? ($!) status\n";
$t->{xferOK} = 0 if ( !$t->{tarBadExitOk} );
}
Regards,
Holger
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
BackupPC-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
