The upload process does too - so it computes a hash of the data that is being read and at the end of the upload compares it to the hash produced by the remote end thus making a very strong integrity check.
That is correct, --checksum does not work with a crypt backend. If your backend supports times then the modtime + size is a reliable way of determining changes. You can always run rclone cryptcheck to see if it it missed any every now and again.
That is correct, --checksum does not work with a crypt backend.
So. What about my suggestion? Would it work?
then the modtime + size is a reliable way
If it would be a reliable way, you would not need --checksum at all. But --checksum is there, and this is for a reason. Because modtime + size is not reliable. I had this case this morning, that rclone sync would not copy anything. But rclone cryptcheck would tell me that there is a file difference. I can’t tell how this happened, but it happened.
Hey - sorry to bring up an old thread. When I perform an rclone copy from one crypt remote to another, I see Checks 0/0. This doesn't bode confidence that checksums were performed. Could you clarify on whats going on? Thanks