When the admin runs “bi purge” they have the option of supplying a bucket_id with the “--bucket-id” command-line argument. This was useful back when resharding did not automatically remove the older bucket index shards (which it now does), which had a different bucket_id from the current bucket index shards. If the admin doesn't supply a bucket_id it assumes the current bucket index shards are to be purged. Because this is generally not wanted, the admin is required to supply the "--yes-i-really-mean-it” command-line argument to verify that they know that this is generally not done. There is no “undo” for “bi purge”, because it removes the metadata objects that contain the bucket listing. The objects should still be readable if you know their names. > After this operation the bucket cannot be listed or removed any more. Knowing the above, what is your goal? Removal/clean-up? Recovery of as much as possible? Both are possible to a degree (not 100%) but the processes are not simple and highly manual. Eric (he/him) > On Feb 20, 2023, at 10:01 AM, Robert Sander <r.sander@xxxxxxxxxxxxxxxxxxx> wrote: > > Hi, > > There is an operation "radosgw-admin bi purge" that removes all bucket index objects for one bucket in the rados gateway. > > What is the undo operation for this? > > After this operation the bucket cannot be listed or removed any more. > > Regards > -- > Robert Sander > Heinlein Consulting GmbH > Schwedter Str. 8/9b, 10119 Berlin > > http://www.heinlein-support.de > > Tel: 030 / 405051-43 > Fax: 030 / 405051-19 > > Zwangsangaben lt. §35a GmbHG: > HRB 220009 B / Amtsgericht Berlin-Charlottenburg, > Geschäftsführer: Peer Heinlein -- Sitz: Berlin > _______________________________________________ > ceph-users mailing list -- ceph-users@xxxxxxx > To unsubscribe send an email to ceph-users-leave@xxxxxxx _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |