By Definition of S3 ETag ，ETag of an object may be a md5 checksum or not, it always depends on the object size. When I copy a big object from custom s3-compatible object storage, corrupted md5 has is reported. I know that --ignore-checksum will work well, but is there some method to allow the check…

How to set checksum cutoff for custom s3-compatible storage?

ncw (Nick Craig-Wood) June 29, 2019, 10:02am 4

If you can just make the Etag not look like an md5sum (32 hex digits) then rclone will ignore it.