rsync to a destination > 8TB problem...

Wayne Davison wayned at
Wed Aug 11 15:57:06 GMT 2004

On Tue, Aug 10, 2004 at 04:41:56PM -0400, Matt Miller wrote:
> rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": Broken pipe
> rsync error: error in rsync protocol data stream (code 12) at io.c(836)

As I just replied to another message on the list, this error just means
that the other side went away for some reason.  What you need to figure
out is why.  The version of rsync in CVS (and in the "nightly" tar
files) tries to grab a dying error from the other side, if possible.
This is coverend on the "known issues" page:

So, I'd recommend trying the CVS version of rsync to see if that gives
you the actual error of what failed.  Alternately (or additionally),
follow the directions on the issues page to get a core dump and/or a
system-call trace from the remote side to get extra information on what
has gone wrong.


More information about the rsync mailing list