Here's something else I noticed: when I stat objects that work via radosgw-admin, the stat info contains a "begin_iter" JSON object with RADOS key info like this "key": { "name": "29/items/WIDE-20110924034843-crawl420/WIDE-20110924065228-02544.warc.gz", "instance": "", "ns": "" } and then "end_iter" with key info like this: "key": { "name": ".8naRUHSG2zfgjqmwLnTPvvY1m6DZsgh_239", "instance": "", "ns": "shadow" } However, when I check the broken 0-byte object, the "begin_iter" and "end_iter" keys look like this: "key": { "name": "29/items/WIDE-20110903143858-crawl428/WIDE-20110903143858-01166.warc.gz.2~m5Y42lPMIeis5qgJAZJfuNnzOKd7lme.1", "instance": "", "ns": "multipart" } [...] "key": { "name": "29/items/WIDE-20110903143858-crawl428/WIDE-20110903143858-01166.warc.gz.2~m5Y42lPMIeis5qgJAZJfuNnzOKd7lme.19", "instance": "", "ns": "multipart" } So, it's the full name plus a suffix and the namespace is multipart, not shadow (or empty). This in itself may just be an artefact of whether the object was uploaded in one go or as a multipart object, but the second difference is that I cannot find any of the multipart objects in my pool's object name dump. I can, however, find the shadow RADOS object of the intact S3 object. _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx