I am using rclone 1.53.1
This "bug" started around the same time I upgraded from rclone 1.51 to rclone 1.53.1. Of course I don't really consider it a bug at all. If anything the hashes were probably always mismatches and now 1.53.1 is better at finding that mismatch?
It is very odd though that I will get one and only one mismatched hash per folder I rclone copy to googledrive.... It doesn't matter if I upload 100 files or 1000 files 100gb or 1000gb... I seem to always end up with one hashes don't match local hash error for one file.
Another thing I personally did that could've triggered this is I started using --bwlimit for my cryptcheck, in the past I only bothered to bandwidth limit my copy command not my cryptcheck command.
Also yes I know running a check right after a copy is pointless because the copy itself performs it's own check... so yeah for YEARS I've done this for NO REASON AT ALL.... but now it's finally doing something so yeah me.
I figured --bwlimit would either work for cryptcheck or it wouldn't have any effect at all, it'd be weird if this "error" was caused by --bwlimit.
I'm not sure how to go about getting a log file for this error though. Because it only happens when I upload a large number of new files to googledrive over a span of many hours. In other words a verbose log file would be absolutely gigantic, and this "error" is not repeatable in teh sense that I can make it happen whenever I want, but roughly once every day or two it will happen, and it's happened now 4or5 times... so I believe it will keep happening, but it might take a dozen hours of uploading to see the error and it will only appear once and when re-run everything will work normally. (It's possible also that I'm ddos'ing googledrive because I have 300megabit internet speed... hence the bwlimit which I'm now setting to --bwlimit 30M but I used to have at --bwlimit 40M)..
edit: and when I say the error isn't repeatable, I mean, it's easily repeatable, if I just re-run the cryptcheck, but if I delete the file off googledrive and rerun both the copy and then the cryptcheck it doesn't reoccur... it seems almost pointless to post an error log for a cryptcheck that I 100% comprehend, what I'm more curious about is the error log on the copy command at the moment the corruption occurs, and how such a thing is even possible, and how copy doesn't catch it with it's post transfer check?
Oh also this is the command:
D:\rclone-v1.53>rclone copy --bwlimit 30M -v --fast-list --drive-chunk-size 128M "D:\Stuff" "cleancachecrypt:D:\Stuff" && rclone cryptcheck --bwlimit 30M --one-way -v --fast-list --drive-chunk-size 128M "D:\Stuff" "cleancrypt:D:\Stuff"
I've been using this command (without the --bwlimit at least) for many years though so I doubt there's anything wrong with it (other than maybe the --bwlimit).
edit2: nevermind, the --one-way cannot be causing the error, it's required for the command to work at all, whoops, I'm tired :-p