rsync - Mar 2015 - Possible Error in rsync 3.0.9

Hi
   I was using rsync with the following options
rsync -aPH --exclude-from=/var/tmp/ignorelist /home/me/ 
/run/media/me/ADATA\ #2/rsync-me/
and I was creating a copy of a home directory on my Linux machine. It 
went along for sometime (some 30,000 files) when it stopped with the 
following message.
--->

Desktop/OSme/Web-Site-Backups/backup-5.4.2014_15-11-43_linux014.tar.gz
   4288446464  78%   32.15MB/s    0:00:36
rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken
pipe (32)
rsync: connection unexpectedly closed (1964386 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(605)
[sender=3.0.9]
[root at puter ~]#

<---
   I suspect, because the 4,288,446,464 is so close to 2^32 that it is 
32 bit limit error of some kind.  It happened twice on the same file.  
The version I am using is rsync.x86_64 version on Fedora 21. It appears 
that although it says it is a 64 bit version something in the code must 
be limited by 32 bit values.
   I could be off track here but I don't think so.  I do not know how to 
raise a Possible Bug Report so I post my concerns here. Thanks...
Robert
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.samba.org/pipermail/rsync/attachments/20150304/a29a0be3/attachment.html>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

It actually doesn't matter if rsync was compiled 32bit or 64bit.  The
check is: rsync --version | grep 64-bit.files

Of course that only means rsync can handle large files.  The OS or
filesystem can still fail.  Essentially, rsync's receiver thread
crashed and the sender thread has no idea why it just knows it stopped
talking.

Might have to resort to running strace on the receiver thread to see
what happens when it breaks.

On 03/04/2015 11:06 PM, Robert wrote:
> Hi I was using rsync with the following options rsync -aPH
> --exclude-from=/var/tmp/ignorelist /home/me/ /run/media/me/ADATA\
> #2/rsync-me/ and I was creating a copy of a home directory on my
> Linux machine.  It went along for sometime (some 30,000 files) when
> it stopped with the following message. --->
> 
> Desktop/OSme/Web-Site-Backups/backup-5.4.2014_15-11-43_linux014.tar.gz
>
> 
4288446464  78%   32.15MB/s    0:00:36
> rsync: writefd_unbuffered failed to write 4 bytes to socket
> [sender]: Broken pipe (32) rsync: connection unexpectedly closed
> (1964386 bytes received so far) [sender] rsync error: error in
> rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] 
> [root at puter ~]#
> 
> <--- I suspect, because the 4,288,446,464 is so close to 2^32 that
> it is 32 bit limit error of some kind.  It happened twice on the
> same file.  The version I am using is rsync.x86_64 version on
> Fedora 21.  It appears that although it says it is a 64 bit version
> something in the code must be limited by 32 bit values. I could be
> off track here but I don't think so.  I do not know how to raise a
> Possible Bug Report so I post my concerns here.  Thanks... Robert
> 
> 
- -- 
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~
	Kevin Korb			Phone:    (407) 252-6853
	Systems Administrator		Internet:
	FutureQuest, Inc.		Kevin at FutureQuest.net  (work)
	Orlando, Florida		kmk at sanitarium.net (personal)
	Web page:			http://www.sanitarium.net/
	PGP public key available on web site.
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlT37/IACgkQVKC1jlbQAQdSsACg0fI9IocPCFCyv/2Ctmj8ovBu
UOkAn3oYretoHUu3wFcBwT+u6rIc108M
=5ESh
-----END PGP SIGNATURE-----