I seem to have this stuck snapshot relating to .ix-virt not sure why it’s appeared and how to get rid of it. I can’t recall making this either.
If anyone has any suggestions or ideas ? greatly appericated.
root@[~]# zfs list
nvme/.ix-virt/deleted/images/3f0c10ba87430f2f0f9a6707b6683684bcb9e8c568260c680e04f1d0c661f9cf 263M 863G 263M legacy
root@[~]# zfs list -t snapshot
NAME USED AVAIL REFER MOUNTPOINT
nvme/.ix-virt/deleted/images/3f0c10ba87430f2f0f9a6707b6683684bcb9e8c568260c680e04f1d0c661f9cf@readonly 8K - 263M -
This is an internal incus snapshot. You should not try to delete it.
Incus images have a @readonly snapshot, this is used as the basis for cloning an instance from the image.
(there are also @copy- and @snap- and @deleted- snaps)
When the image itself is deleted, it may have an active clone. If this is the case, then the image is moved into a deleted dataset… a bit like a trash bin… and then when all the related clones are deleted… then the image is actually deleted.
you can use zfs get -o clones nvme/.ix-virt/deleted/images/3f0c10ba87430f2f0f9a6707b6683684bcb9e8c568260c680e04f1d0c661f9cf@readonly to see which instances are using the image.
Or you can ignore it… which is what you’re supposed to do with the .ix-virt dataset
greatly appericated.
