[Bug 2187] rsync large file getting verification failed using -z

[samba-bugs at samba.org]

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


stix at stix.homeunix.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |stix at stix.homeunix.net




------- Additional Comments From stix at stix.homeunix.net  2005-01-21 05:36 -------
I can confirm this bug under both AIX 5.2 and NetBSD 2.0, with 2.6.3 and CVS-HEAD as of 2005-
01-21. I also have a somewhat manageable test case which results in "verification failed" - a pair 
of 10 MB files available at:

ftp://stix.homeunix.net/pub/rsyncbug2187/file1.gz
ftp://stix.homeunix.net/pub/rsyncbug2187/file2.gz

Test blocksize is as reported by rsync on an actual transfer of a file a little over 4 GB. Test 
command was:

ksh$ rsync -B 66552 -acvvz --stats --inplace -e /usr/bin/rsh /tmp/z/file1 localhost:/tmp/z/file2 
opening connection using /usr/bin/rsh localhost rsync --server -vvlogDtprcz -B66552 --inplace . 
/tmp/z/file2 
building file list ... 
[sender] expand file_list to 131072 bytes, did move
done
delta transmission enabled
file1
WARNING: /tmp/z/file2 failed verification -- update retained (will try again).
file1
total: matches=306  tag_hits=1898  false_alarms=0 data=665520
ERROR: /tmp/z/file2 failed verification -- update retained.

Number of files: 1
Number of files transferred: 2
Total file size: 10485760 bytes
Total transferred file size: 20971520 bytes
Literal data: 665520 bytes
Matched data: 20306000 bytes
File list size: 61
Total bytes sent: 290611
Total bytes received: 4168

sent 290611 bytes  received 4168 bytes  196519.33 bytes/sec
total size is 10485760  speedup is 35.57
rsync error: some files could not be transferred (code 23) at main.c(702)
ksh$ cmp /tmp/z/file?
/tmp/z/file1 /tmp/z/file2 differ: char 3726913, line 11513


-- 
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.