Issue with bwlimit after resuming a partial transfer due to a communication break

Wayne Davison wayned at
Sat Jan 22 10:31:29 MST 2011

On Sat, Jan 22, 2011 at 2:22 AM, Alistair Dsouza <alistaird at>wrote:

> Literal data: 6,496 bytes

That is how much literal data rsync had to send to finish the file, so it is
not surprising that it finished quickly.  See also the Total bytes received
(about 40K), so it would not be surprising to have a 10K/sec limited
connection finish in 4 seconds (in the example you cited it took longer than
than, only averaging 5K/sec, presumably due to all the copying of basis-file
data that went on).

So, in your testing, be sure to not use a file that contains repetitive
data.  When sending a new file, only the -z option helps rsync to send
repetitive data with reduced bandwidth.  But when copying over a partial
basis file, the normal checksum matching will copy local basis-file data for
both the partial data and for any matching chunks in the unsent part of the
file that match chunks in the earlier part of the file.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the rsync mailing list