Ah of course, thanks for pointing that out, I somehow didn't think of
the remaining clones.
Thanks a lot!
Zitat von Ilya Dryomov <idryomov@xxxxxxxxx>:
On Fri, Dec 15, 2023 at 12:52 PM Eugen Block <eblock@xxxxxx> wrote:
Hi,
I've been searching and trying things but to no avail yet.
This is uncritical because it's a test cluster only, but I'd still
like to have a solution in case this somehow will make it into our
production clusters.
It's an Openstack Victoria Cloud with Ceph backend. If one tries to
remove a glance image (openstack image delete {UUID}' which usually
has a protected snapshot it will fail to do so, but apparently the
snapshot is actually moved to the trash namespace. And since it is
protected, I can't remove it:
storage01:~ # rbd -p images snap ls
278ffe2b-67a7-40d0-87b7-903f2fc9c3b4 --all
SNAPID NAME SIZE PROTECTED
TIMESTAMP NAMESPACE
159 1a97db13-307e-4820-8dc2-8549e9ba1ad7 39 MiB Thu
Dec 14 08:29:56 2023 trash (snap)
storage01:~ # rbd snap rm --snap-id 159
images/278ffe2b-67a7-40d0-87b7-903f2fc9c3b4
rbd: snapshot id 159 is protected from removal.
storage01:~ # rbd snap ls images/278ffe2b-67a7-40d0-87b7-903f2fc9c3b4
storage01:~ #
This is a small image and only a test environment, but these orphans
could potentially fill up lots of space. In a newer openstack version
(I tried with Antelope) this doesn't seem to work like that anymore,
so that's good. But how would I get rid of that trash snapshot in this
cluster?
Hi Eugen,
This means that there is at least one clone based off of that snapshot.
You should be able to identify it with:
$ rbd children --all --snap-id 159
images/278ffe2b-67a7-40d0-87b7-903f2fc9c3b4
Get rid of the clone(s) and the snapshot should get removed
automatically.
Thanks,
Ilya
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
