rsync error: error in rsync protocol data stream (code 12) at io.c(140)

Greenfelder, John - John T John.T.Greenfelder at lowes.com
Mon Oct 29 13:52:14 GMT 2007


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-labs.com
<mailto:rsync%40lists.samba.org?Subject=rsync%20error%3A%20error%20in%20
rsync%20protocol%20data%20stream%20%28code%2012%29%20at%20io.c%28140%29&
In-Reply-To=3C7CC328.EBEFFDE1%40amtrak.co.uk> 
Thu Feb 28 05:54:15 EST 2002 

*	Previous message: rsync error: error in rsync protocol data
stream (code 12) at io.c(140)
<http://lists.samba.org/archive/rsync/2002-February/001717.html> 
*	Next message: rsync error: error in rsync protocol data stream
(code 12) at io.c(140)
<http://lists.samba.org/archive/rsync/2002-February/001727.html> 
*	Messages sorted by: [ date ]
<http://lists.samba.org/archive/rsync/2002-February/date.html#1716>  [
thread ]
<http://lists.samba.org/archive/rsync/2002-February/thread.html#1716>  [
subject ]
<http://lists.samba.org/archive/rsync/2002-February/subject.html#1716>
[ author ]
<http://lists.samba.org/archive/rsync/2002-February/author.html#1716>  

________________________________

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 so low on memory that it's
printing
the default error message "Success" rather the real one.  An argument
against
the out-of-virtual-memory theory is that I don't see write_file()
calling
malloc as a side effect anywhere.  Maybe the kernel itself is out of
memory.
 
- Dave
 
 
On Wed, Feb 27, 2002 at 11:29:44AM +0000, Andrew McGregor wrote:
> Hi,
> 
> I have installed 2.5.3pre1 but have (virtually) the same error:
> 
> | 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)
> 
> The command I run is:
> 
> | andrewm at massachusetts
<http://lists.samba.org/mailman/listinfo/rsync> :~/test-rsync$ rsync -v
--progress
> conn:/home/andrewm/test-rsync/tree/*
/home/andrewm/test-rsync/rsh_tree/
> 
> Are there other debug options I can use?  Or possibly compile the
source
> differently to help prove/disprove this as a bug/local system problem?
> 
> Regards
> 
> Andrew McGregor

 

 

John Greenfelder

System Engineer II

Lowes Companies

 (336) 658-3741

 

-------------- next part --------------
HTML attachment scrubbed and removed


More information about the rsync mailing list