connection unexpectedly closed (201 bytes read so far)
| rsync error: error in rsync protocol data stream (code 12) at
io.c(140)
I have only just subscribed to this mailing list, so apologies if I have
missed any discussion on this topic. A MHonArc conversion of rsync.mbox
(from rsync.samba.org) sugge
This is an extrememly old post, so it might not be of any use anymore.
I encountered this same error, and the problem ended up being a full
filesystem (my destination filled up before completion).
rsync error: error in rsync protocol data stream (code 12) at io.c(140)
Dave Dykstra dwd at bell
er
> -v . "/home/andrewm/test-rsync/tree/*"
> | large_file2
> | write failed on large_file2 : Success:06
> | rsync error: error in file IO (code 11) at receiver.c(271)
> | rsync: connection unexpectedly closed (201 bytes read so far)
> | rsync error: error in rsync protocol data
e IO (code 11) at receiver.c(271)
> > | rsync: connection unexpectedly closed (201 bytes read so far)
> > | rsync error: error in rsync protocol data stream (code 12) at
> > io.c(140)
> >
> > I have only just subscribed to this mailing list, so apologies if I hav
> | write failed on large_file2 : Success:12
> | rsync error: error in file IO (code 11) at receiver.c(271)
> | rsync: connection unexpectedly closed (201 bytes read so far)
> | rsync error: error in rsync protocol data stream (code 12) at io.c(151)
Hi,
I would like to humbly apologies ... one o
connection using rsh conn /usr/bin/rsync --server --sender
> > > -v . "/home/andrewm/test-rsync/tree/*"
> > > | large_file2
> > > | write failed on large_file2 : Success:06
> > > | rsync error: error in file IO (code 11) at receiver.c(271)
> > >
On Wed, Feb 27, 2002 at 02:57:59PM +, Andrew McGregor wrote:
> > | write failed on large_file2 : Success:12
> > | rsync error: error in file IO (code 11) at receiver.c(271)
> > | rsync: connection unexpectedly closed (201 bytes read so far)
> > | rsync error: error in rsync protocol data strea
Dave Dykstra wrote:
>
> The rsync code that prints that error on line 270 of receiver.c is printing
> strerror(errno), and that error message "Success:12" looks very strange to
> me. If the 12 indicates errno, that's an ENOMEM error. Is your system out
> of virtual address space? Maybe it is s
Dave Dykstra wrote:
>
> The rsync code that prints that error on line 270 of receiver.c is printing
> strerror(errno), and that error message "Success:12" looks very strange to
> me. If the 12 indicates errno, that's an ENOMEM error. Is your system out
> of virtual address space? Maybe it is s
