Strangely fast run without error
Cenedese at indel.ch
Mon Jan 6 09:03:17 MST 2014
>> I have a NAS with rsync 3.0.3pre1. I know that is not new,
>> but a NAS is not easy to update. This usually works fine.
>> I have set up jobs to backup various stuff to another NAS.
>> This is the statistics of one run. Though there were seen
>> files (file size, vmware images) it finished almost immediately
>> which lead to the funny transfer speed.
>> receiving incremental file list
>> Number of files: 125
>> Number of files transferred: 0
>> Total file size: 25013819983 bytes
>> Total transferred file size: 0 bytes
>> Literal data: 0 bytes
>> Matched data: 0 bytes
>> File list size: 2382
>> File list generation time: 0.001 seconds
>> File list transfer time: 0.000 seconds
>> Total bytes sent: 63
>> Total bytes received: 2425
>> sent 63 bytes received 2425 bytes ,')* bytes/sec
>> total size is 25013819983 speedup is 10053786.17
>> This was a one time only thing, afterwards it worked
>> fine again. Still might be interesting to know what it was
>> that rsync finished so quickly without an error.
>This is what it looks like when rsync thinks everything is up to date on
>the target. It didn't transfer anything. that's why it was so fast. You
>would need to post your rsync command and other relevant data for anyone
>to be able to diagnose this further.
In other runs where there's also nothing to do it looks like this:
receiving incremental file list
Number of files: 125
Number of files transferred: 0
Total file size: 25013819983 bytes
Total transferred file size: 0 bytes
Literal data: 0 bytes
Matched data: 0 bytes
File list size: 2382
File list generation time: 0.001 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 63
Total bytes received: 2425
sent 63 bytes received 2425 bytes 4976.00 bytes/sec
total size is 25013819983 speedup is 10053786.17
The same numbers except for the transfer rate. Might be an
issue when rounding numbers so not visible from the stat output.
Doesn't bother me that much as long as it works correctly. I just
thought I report it here in case that gives a hint to a bug.
More information about the rsync