This is the mail archive of the
mailing list for the Cygwin project.
Re: Rsync issue - can it handle files larger than 2 gigabytes?
- From: "Larry Hall (RFK Partners, Inc)" <lhall at rfk dot com>
- To: Michael Bourgon <michael_bourgon at yahoo dot com>,cygwin at cygwin dot com
- Date: Thu, 26 Dec 2002 18:58:20 -0500
- Subject: Re: Rsync issue - can it handle files larger than 2 gigabytes?
At 01:06 PM 12/26/2002, Michael Bourgon wrote:
>I'm trying to sync a 2.21 gigabyte file (so, a "large
>file") between Win2k and Win2k, where the client is
>pushing the file to the server (which is running
>"rsync --daemon --no-detach").
>It fails, and to isolate the problem, I tried cp'ing
> cp /cygdrive/f/MY_db_200212252102.BAK /tmp
>which works successfully. I then tried to rsync the
> rsync -a -vv -W --include=MY_db_200212252102.BAK
>--exclude=*.* /cygdrive/f/ /tmp
>It appears to replace the file with a 0-byte file.
>Here's the log from when it runs:
>building file list ...
>expand file_list to 4000 bytes, did move
>including file MY_db_200212252102.BAK because of
>total: matches=0 tag_hits=0 false_alarms=0
>wrote 150 bytes read 36 bytes 124.00 bytes/sec
>total size is -1911686656 speedup is -10277885.25
>Does anyone know if there's anything I need to do to
>get large file support? (I did have 4.58 gig free, so
>it wasn't due to lack of space) Thanks.
Looks to me like you're running into 32-bit integer overflows.
While Cygwin internals don't support 64-bit either, judging from
the output above, I'm guessing that rsync problem you're seeing is
internal to rsync. A closer look at the code would help you determine
that for sure. In any case, this is an indication that file sizes
beyond 2GB don't work.
Larry Hall firstname.lastname@example.org
RFK Partners, Inc. http://www.rfk.com
838 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html