Ceph » rbd

I look forward to try fixing this bug? Can I get a recipe to reproduce the bug?

Create and fill images that utilize a data pool (i.e. rbd create --size 10G --data-pool=datapool rbd/image). If you move those images to the trash and attempt to delete them using a purge threshold, only the "rbd" pool utilization will be checked instead of the "datapool" pool.

Well, what's the difference between the base pool and the data pool? I did couldn't find anything that would tell me the difference between these in docs, source code and web. Is it, somehow, related to tiering?

And, ideally it should check for both of them or either (depending on the user/situation)?

It's related to where the image data is stored -- which would be the bulk storage usage source for a trashed image.

Does it mean support an option like:

rbd trash purge <pool-name> --threshold '<x>' --data-pool=<data-pool-name>

..and it looks for pool utilization in <data-pool-name> as that would be the source for trashed images?

@Mahati: I would think it should just be implicit. It could loop through all the trashed images whose deferment end time is in the past and compute a set of (data) pools in-use by the images. For each pool in the set, delete trashed images in that (data) pool until that pool's threshold is met.