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

[Andrew McGregor]

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 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
> 

Hi,

I think the below extract from an ftp session between two Debian boxes
proves
this is not an rsync problem as the error is too similar to be anything
else.
The file is a ~500mb tarball.

| ftp> put Disk1.tar.gz
| local: Disk1.tar.gz remote: Disk1.tar.gz
| 200 PORT command successful.
| 150 Opening BINARY mode data connection for Disk1.tar.gz.
| netout: Broken pipe
| 452 Error writing file: Success.
| ftp> 

[OT] This reminds me of Dr. Damian Conway's superposition Perl module
where 
it returns both true and false at the same time ;)

http://search.cpan.org/doc/DCONWAY/Quantum-Superpositions-1.03/lib/Quantum/Superpositions.pm

| andrewm at massachusetts:~$ df -k
| Filesystem           1k-blocks      Used Available Use% Mounted on
| /dev/hda6              1968588   1868644         0 100% /

Unfortunately, I can't confirm whether this is Linux or Debian
obfuscating
things.

Once again, apologies for any inconvenience.

Regards

Andy