Hi!
Am 09.12.17, 00:19 schrieb "Robin H. Johnson" <robbat2@xxxxxxxxxx>:
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.
Yes indeed. Running "radosgw-admin bi list" results in an incomplete 300MB JSON file, before it freezes.
FYI: "radosgw-admin bi get" returns "no such file or directory" immediately.
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.
I'll try the first variant, maybe it at least removes some of the cruft.
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).
I am all ears, as long as it won't touch the other healty buckets __
Thanks,
Martin
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
