Support for large files

OK, I'll test in the next day or so and advise.
Thank you.

Vaughan

Hi,
rsync fell over on the same file, in the same place I think (or certainly close to it).

Bytes transferred of the file was: 4,294,705,152

Error message:
rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown" : Connection reset by peer (104)
rsync: read error: Connection reset by peer (104)
rsync error: error in rsync protocol data stream (code 12) at io.c(584)

Vaughan

Hi,
Unfortunately I am also seeing similar errors on much smaller files (600k):

rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown" : Connection reset by peer (104)
rsync: read error: Connection reset by peer (104)
rsync error: error in rsync protocol data stream (code 12) at io.c(570)

Files vary, and the io.c(value) changes, but the substance of the error is consistent. I have tried disabling all switches apart from -a, and it makes no difference.

This is with the v2 client and the newer version that you compiled, I will try v1.3, and see if that makes any difference.

I can also post the sending_file log for an example file if that might be useful.

Hi,
The 1.3 rsync.exe has identical symptoms. I don't understand it. I had successfully rsync'ed this directory tree a number of times previously.

Trying to think of the things that I have changed. I guess I'll go back to 1.3 server and see if that makes any difference.

Vaughan

Hi,
I did a test. cwRsync 2.0.0 client and server are installed on windows 2003 machines. I tried to copy a 6.22 GB image file from client to server. First run took about 1h 20m and is completed successfully:

F:\image\data\w2003-mf>cwrsync (batch file running rsync --progress -v test3.dat xxxxx::test with cygwin=nontsec)
test3.dat
6684591156 100% 1.27MB/s 1:23:28 (1, 100.0% of 1)

sent 6685407238 bytes received 38 bytes 1334279.47 bytes/sec
total size is 6684591156 speedup is 1.00

There was about 2.5 GB free space on server side. I then tried to run the same command again. I got following error message:

F:\image\data\w2003-mf>cwrsync
test3.dat
rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown" : Connection reset by peer (104)
rsync: read error: Connection reset by peer (104)
rsync error: error in rsync protocol data stream (code 12) at io.c(584)

I observed that rsync on server side used temporary disk space and the problem above appeared because there were no free space on disk. I then run rsync again with --inplace option and the operation is completed successfully:

F:\image\data\w2003-mf>cwrsync
opening tcp connection to xxxxx port 873
opening connection using --server -vv --inplace . test
test3.dat
6684591156 100% 23.07MB/s 0:04:36 (1, 100.0% of 1)
total: matches=81767 tag_hits=81767 false_alarms=3 data=0

sent 327158 bytes received 654174 bytes 1454.90 bytes/sec
total size is 6684591156 speedup is 6811.75

Hi Tev,
Well this sounds promising for a few reasons:

1. I went back to v1.3 on both the client and the server, and it didn't make any difference.

2. At the site where I was trying to send the 5GB file, there isn't heaps of free space, so this is consistent with your observations.

3. At the site where I am seeing the problem with the 600K file, there isn't much free space on the server either (doh!), it's more apparent here, and I should have thought to check for that.

I am sure you're right about this. Thanks.

Vaughan