I believe the Etag is expected to have an md5sum of the payload, but in the case of multipart uploads, Amazon stores the md5sum of the most recent piece uploaded, with "-" and the piece number appended. You saw that your upload was in four pieces, and "-4" was appended to what was supposed to be the MD5 checksum.
The problem is still present in s3cmd 1.5.3, and I suspect it is a mistake made by Amazon, not by the s3cmd developers. One suggested workaround was to use 's3cmd mv realname baloney ; s3cmd mv baloney realname ' to force Amazon S3 to recompute the md5sum... but IIRC this doesn't really move (or re-key) the file so much as download, reupload, then delete the original, so if the file is larger than multipart-chunk-size then it will reupload in pieces, recreating the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1479967 Title: md5sum mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s3cmd/+bug/1479967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
