addady at active.co.il
Wed Mar 12 07:21:18 EST 2003
It happen to me also
rsync from cygwin 2.5-6 to Linux 2.5-6.
On the client side I got:
rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown":
Connection reset by peer
rsync error: error in rsync protocol data stream (code 12) at io.c(515)
On the server log:
2003/03/11 14:08:30  write failed on dir/file : Success
2003/03/11 14:08:30  rsync error: error in file IO (code 11) at
2003/03/11 14:08:30  rsync: connection unexpectedly closed (20646
bytes read so far)
2003/03/11 14:08:30  rsync error: error in rsync protocol data stream
(code 12) at io.c(165)
adding -T /tmp workarund it !
----- Original Message -----
From: "Wayne Davison" <wayned at users.sourceforge.net>
To: "James Sewell" <james.sewell at tait.co.nz>
Cc: <rsync at lists.samba.org>
Sent: Sunday, March 02, 2003 1:32 AM
Subject: Re: Rsync problem
> On Sun, Mar 02, 2003 at 11:51:39AM +1300, James Sewell wrote:
> > I just fixed this problem by adding -T /tmp.
> This makes me wonder if there was some kind of a write problem of the
> temp file into the destination directory. Keep in mind that scp writes
> directly over the destination file, while rsync by default first writes
> a temporary file in the same dir and then renames it. Using the -T
> option causes the temp file to go into a different dir.
> Why you didn't get a better error message is probably the most pertinent
> question. It might be that the remote rsync crashed. In such a case
> you have to take extra steps to try to figure out why the remote process
> is dying (like accessing the remote core file, if one exists).
> To unsubscribe or change options:
> Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
More information about the rsync