Bug 5167 - The size of the transferred part of a file exceeds 2 Gb.
The size of the transferred part of a file exceeds 2 Gb.
Status: RESOLVED WORKSFORME
Product: rsync
Classification: Unclassified
Component: core
2.6.9
x86 Linux
: P3 normal
: ---
Assigned To: Wayne Davison
Rsync QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-12-29 04:55 UTC by Sergey Larionov
Modified: 2009-03-16 16:21 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sergey Larionov 2007-12-29 04:55:00 UTC
rsync -az --timeout=90 --partial --port=873 --password-file=pasword.tmp
root@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@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.  :-(((((
Comment 1 Paul Slootman 2007-12-29 07:39:31 UTC
Please show the output of rsync --version
It should show something like:
Capabilities:
    64-bit files, ...

If it doesn't, your version of rsync was simply not compiled with support for large files.
Comment 2 Wayne Davison 2008-01-12 11:58:00 UTC
Large files work fine on an rsync compiled with a large-file library.
Comment 3 Sergey Larionov 2008-01-13 23:19:40 UTC
> Please show the output of rsync --version
Yes :

$ rsync --version
rsync  version 2.6.9  protocol version 29
Copyright (C) 1996-2006 by Andrew Tridgell, Wayne Davison, and others.
<http://rsync.samba.org/>
Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles,
              inplace, IPv6, 64-bit system inums, 64-bit internal inums
Comment 4 Sergey Larionov 2008-01-13 23:36:12 UTC
> Large files work fine on an rsync compiled with a large-file library.
   What is "large-file library" ?
Comment 5 Jerome 2009-03-16 16:21:29 UTC
I ran into a similar problem trying to backup a >4GB to a truecrypt partition. Truecrypt used FAT32 which doesn't support files larger than 4GB so check your filesystem.