Marty writes:
> With one host I intermittently get the following error message with two
> different servers running different versions of backuppc:
>
> Tar exited with error 256 () status
>
> Judging from the Xferlog contents, the failure seems to occur only after the
> last files are transmitted successfully. I have seen rare intermittent
> failures
> before, but lately they seem to be more frequent, with one failing several
> consecutive attempts. The client host has recently increased its size by
> several gigabytes. The servers are Debian Sarge systems and the client is
> running Debian Etch. There is plenty of spare disk space on the servers.
> Thanks
> in advance for any ideas or suggestions.
Please look this up on the mail list. This was fixed in 3.0.0:
* Fixes to lib/BackupPC/Xfer/Tar.pm for tar 1.16: allow 1
(ie: 256) as a successful exit status and match "Total
bytes read" message for restores. First reported by
Torsten Sadowski and debugged by Ralf Gross and Holger
Parplies.
Craig
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
BackupPC-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
