Hendrik Friedel wrote:
>
> I found the source of the problem:
> http://samba.anu.edu.au/rsync/issues.html
>  
> Q: Why does my transfer die with something like the following error? 
> 
> rsync: error writing 4 unbuffered bytes - exiting: Broken pipe
> 
> rsync error: error in rsync protocol data stream (code 12) at io.c(463)
> 
> 
> There are several common causes for a remote rsync process going away: 
> 
> *     The destination disk is full (remember that you need at least the
> size of the largest file that needs to be updated available in free disk
> space for the transfer to succeed). 
> 
> Bingo. That's it. I would have hoped for a more specific error-Message,
> though. 
> Maybe it would be advisable to make Backuppc check, if the disc is full in
> case of a "child exited prematurely" error and let BackupPc display a
> message "child exited prematurely, Your disc is full" message?! 

I think this situation is usually avoided because backuppc defaults to 
not starting a backup if the disk is already 95% full.  You must have 
some files that are relatively large compared to the backuppc archive 
file system - or you were too full for a scheduled run but forced it 
manually.

-- 
   Les Mikesell
     lesmikesell AT gmail DOT com


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/