hello and thanks for taking the time to read this.
I am a newbiew, have been using rclone and testing it.
I read that ‘MD5/SHA1 hashes checked at all times’ but whenever I look at the logfile, I always see that no files are checked. I read on the forum about in some cases, checksum is not fone for large files.
So the file I uploaded is just three bytes.
can someone help me understand if all files are checked at all times or do I need to run a rclone check after a rclone copy?
there seems to be a lot of confusion in the forum about when checksums are used and when they are not.
perhaps someone can create a dedicated faq about it.
thanks but the main webpage states that all transfer are checked but that does not seem to be true.
and how do I disable that picure of yourself in the forum?
thanks the the quick reply.
i am stil confused as the hompage is clear
"MD5/SHA1 hashes checked at all times for file integrity’
at ALL times, but clearly this is not the case, correct?
and also the claim ‘rsync for the cloud’ does not seem to be true as rclone does not do delta updates and has nothing at all in common with rsync, correct?
i am liking rlcone and it is very easy to use but the homepage should be accurate and truthful about what the software is and does.
thanks and this is my last attempt to clarify. rclone is nothing at all like rsync.
most any software can copy and sync ENTIRE files, that is trivial and easy to implement.
.
rclone:if only one byte of a one gigabye file changes, rclone will copy the entire one gigabyte file, not just the one byte that changed.
rsync: can only update the one byte, not the entire one gigabyte.
I like rclone and use it everyday but please, do not compare rclone to rsync… that is an insult to rsync.
"The recipient splits its copy of the file into chunks and computes two checksums for each chunk: the MD5 hash, and a weaker but easier to compute ‘rolling checksum’.[23] It sends these checksums to the sender.
The sender quickly computes the rolling checksum for each chunk in its version of the file; if they differ, it must be sent. If they’re the same, the sender uses the more computationally expensive MD5 hash to verify the chunks are the same’