This just started happening a few weeks ago when a lot of large, (larger than 1g) files started resulting in the error stated in the title. This happens somewhat randomly in the transferring process, happening around ~50% into the way of completing the copy. I’m currently in the process of using an older version of rclone to see how it goes(version 1.39, go1.9.2) I’m using windows x64 and it is a google drive crypt remote. I’ve searched the forums and couldn’t find any concrete solution or cause of this problem.
the lines above and below are just normal debug lines, with “sending chunk… length…” information.
This happened around 18% into the copy of a 2.1G file.
We haven't found a solution for this yet. Ideally I'd like to be able to reproduce the problem with a simple go program then I can report it to the go team. It might be a hardware problem though causing corrupted ethernet packets.
Yes, after if fails, it skips to copy another file then retries the failed files, it doesn’t seem like the retried ones fail though. I have a combination of files larger than ~1G and less than 1G but overall there is ~10% error. As in rclone will report 10 errors in 100 transferred
I can try downloading like 50GB with rclone, I’m not sure how to do that with other programs though, since maybe it’s something wrong with decrypt/encrypt? There wouldn’t be any point downloading encrypted files right? Also I noticed that smaller files also sometimes fail (~200MB), I probably just didn’t notice it since it’s easier to see larger files fail.
That specific error is corruption in network transfer detected by the TLS/https layer. So downloading files with https using curl should reproduce it if it is a hardware problem.