DO NOT REPLY [Bug 5167] New: The size of the transferred part of a file exceeds 2 Gb.

[samba-bugs at samba.org]

https://bugzilla.samba.org/show_bug.cgi?id=5167

           Summary: The size of the transferred part of a file exceeds 2 Gb.
           Product: rsync
           Version: 2.6.9
          Platform: x86
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: core
        AssignedTo: wayned at samba.org
        ReportedBy: slarionov at xperinet.com
         QAContact: rsync-qa at samba.org


rsync -az --timeout=90 --partial --port=873 --password-file=pasword.tmp
root at 192.168.0.99::'mirv/vol0//17 - Check day.vob'
'/media/video/recordings/vol0//17 - Check day.vob'

10 minutes later:

I do Ctrl/C
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at
rsync.c(276) [generator=2.6.9]
$ ls -l 17*
-rwxrwxrwx 1 lary lary 2124622946 Dec 25 12:55 17 - Check day.vob

The limit 2 GB is exceeded.

rsync -az --timeout=90 --partial --port=873 --password-file=pasword.tmp
root at 192.168.0.99::'mirv/vol0//17 - Check day.vob'
'/media/video/recordings/vol0//17 - Check day.vob'

I observed of the program rsync by iptraf. 
After transfer 335 Kb data transfer stopped and error messages stood
out. 
On a server : 
Dec 25 07:15:03 mirv-99 rsyncd[26952]: rsync: writefd_unbuffered failed
to write 4 bytes [sender]: Broken pipe (32)
Dec 25 07:15:03 mirv-99 rsyncd[26952]: rsync error: error in rsync
protocol data stream (code 12) at io.c(1122) [sender=2.6.9]

On the client :
io timeout after 120 seconds -- exiting
rsync error: timeout in data send/receive (code 30) at io.c(165)
[receiver=2.6.9]
rsync: connection unexpectedly closed (65 bytes received so far)
[generator]
rsync error: error in rsync protocol data stream (code 12) at io.c(453)
[generator=2.6.9]

I have repeated experiment 3 times.  :-(((((


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.