TIL rsync's best checksum is md5. This means that if you're conducting a supply chain attack on a system which uses rsync to keep the mirrors in sync, you could pollute the mirrors w/ bad copies that collide w/ md5 and even rsync --checksum wouldn't know they were modified.
Conversation
Replying to
It also does the entire thing in advance and it entirely blocks progress on uploading while calculating all the checksums. It's very impractical for syncing incremental changes to a very large overall amount of data. It's a lot more than just not being parallel / async.
1
1
2
I find rsync very impractical with checksums enabled. For large amounts of data, you need to use -t and rely on the last modified date + size checks to make it happen in a reasonable amount of time. Can use checksum mode as an integrity check but probably not for regular usage.
2
2
Replying to
I mean, it really shouldn't be, modern secure checksums can be run at 1 GB/sec+ and modern disks run at 200+MB/sec each (spinning rust, SSD/nvme even faster), I mean yes, if you're sync'ing a lot of data, it'll take time.
1
Replying to
It has a particularly slow implementation and as you pointed out it's entirely serial so it's really bad at using the available CPU and I/O resources. Maxing out I/O while doing a ton of CPU work really requires at least using a large thread pool. Don't need fancy AIO.
2
1
I find the main issue is that it simply waits to calculate all of those hashes before it actually starts doing any of the syncing work. It should really be doing as much syncing as it can based on changed file / directory structure and times / sizes before worrying about that.
The checksums should be treated as a way to find corrupted data. It's a lower priority than the more obvious syncing work and it can be done in parallel. It only has to do that for files which look like they shouldn't have any changes. It doesn't do anything like that though.
1
Replying to
Yeah, cvsup used the trick of just sorting all the names in the directory, and send them as it progressed, as soon as there was a mismatch between the two, it'd know if it was an addition or a removal, and didn't need to wait even for a large directory to be received.