If you use 'radosgw-admin bi list', you can get a listing of the raw bucket index. I'll bet that the objects aren't being shown at the S3 layer because something is wrong with them. But since they are in the bi-list, you'll get 409 BucketNotEmpty. At this point, I've found two different approaches, depending how much you want to do in rgw vs the S3 APIs. A) S3 APIs: upload new zero-byte files that match all names from the bucket index. Then delete them. B) 'radosgw-admin object unlink'. This got messy with big multipart items. Other things that can stop deletion of buckets that look empty: - open/incomplete multipart uploads: run Abort Multipart Upload on each upload. - bucket subresources (cors, website) [iirc this was a bug that got fixed]. I have not personally played with editing the bi entries in cases like this. There are more drastic ways to delete the entry points into a bucket as well (but it would otherwise leave the mess around). -- Robin Hugh Johnson Gentoo Linux: Dev, Infra Lead, Foundation Asst. Treasurer E-Mail : robbat2@xxxxxxxxxx GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85 GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136
Attachment:
signature.asc
Description: Digital signature
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
