I have a question, if you could spare some to time check please. After upgrading o the latest beta which fixed some issues with s3 backend, I can no longer see the key "x-amz-meta-md5chksum" filled in my recent uploads. As I could check, previous uploads using v1.50.2 have this information. Is this something I should worry about, concerning the integrity of the uploaded files?
What is your rclone version (output from rclone version)
Which OS you are using and how many bits (eg Windows 7, 64 bit)
Windows Server 2012 R2 STD x64
Which cloud storage system are you using? (eg Google Drive)
The command you were trying to run (eg rclone copy /tmp remote:tmp)
Just did some testing with v1.50.2, which showed the same results, no "x-amz-meta-md5chksum" on the tag, so I might have correlated the behavior to the wrong cause. It's very odd, since files from 28/12/2019 on S3 (uploaded with rclone) have it.
The only other change recently I've made was to enable bucket versioning, maybe this was the cause? But again, I am just trying to know if this is an issue, or if I should not be worried at all.
Files of sizes below --s3-upload-cutoff (200M) by default won't have x-amz-meta-md5chksum however they should have an Etag which is a valid md5sum which is why rclone doesn't bother computing the metadata for those files.
The Etag is present in all uploads above, as far as I could check. What I can see is that prior to 01/02/2020, all uploads (from 200Mb up to 700Gb) have x-amz-meta-md5chksum, the latest do not have it.
Again, very odd behavior. I'm not sure if this is rclone version related or bucket versioning related.
I can see that the headers are back in the log and in AWS Metadata aswell ! This was a multipart upload, which means that it work correctly for all kinds of load. See the evidences below, and I appreciate your help once again.