can't delete snapshop - This operation cannot be performed because the system does not manage this VDI

Andi79

I have problems on deleting an VM snapshot. it seems that it it's linked to a active VDI of a VM, but when i try to delete it in XOA nothing happens. I tried to delete it on CLI with that result:

#xe vdi-destroy uuid=80304704-a164-4fe3-bc15-c776b2d4cc2b
This operation cannot be performed because the system does not manage this VDI
vdi: 80304704-a164-4fe3-bc15-c776b2d4cc2b (vm-test-disk)

#xe vdi-list
uuid ( RO)                : 80304704-a164-4fe3-bc15-c776b2d4cc2b
name-label ( RW): vm-test-disk
name-description ( RW): 
sr-uuid ( RO): c29b2189-edf2-8349-d964-381431c48be1
virtual-size ( RO): 214748364800
sharable ( RO): false
read-only ( RO): true

Any idea how I can delete this snapshot?

olivierlambert

It's probably a base copy or something in the chain. It will be automatically removed by the garbage collector. If it's not, then check your storage log for why it's not.

Andi79

@olivierlambert

i had success with a vdi-forget. thanks

Andi79

@olivierlambert
ok, not 100% success.

after running the vdi-forget it does not work to free up the space after clicking reclaim freed space. And when I rescan the vdi it appears again.

is there any risk when i delete this lv directly by lvremove

--- Logical volume ---
LV Path                /dev/VG_XenStorage-c29b2189-edf2-8349-d964-381431c48be1/VHD-80304704-a164-4fe3-bc15-c776b2d4cc2b
LV Name                VHD-80304704-a164-4fe3-bc15-c776b2d4cc2b
VG Name                VG_XenStorage-c29b2189-edf2-8349-d964-381431c48be1
LV UUID                glbGl8-UhKX-AxHV-0YJm-hy8e-sIe6-kNU2tZ
LV Write Access        read only
LV Creation host, time host2-neu, 2022-06-16 18:29:45 +0200
LV Status              available
# open                 1
LV Size                <190,35 GiB
Current LE             48729
Segments               1
Allocation             inherit
Read ahead sectors     auto
- currently set to     256
Block device           252:2

olivierlambert

NEVER do that. If the VDI is there, it's for a reason. It's part of a chain for example.

Again, same than before: let the garbage collector remove it, and if it doesn't, investigate why.

Andi79

@olivierlambert

how can i start it manually? As far as I understand GC starts in a case of an SR Scan, but when I do this it restores the forgotten vdi.

in some way it seems to be linked as basecopy snapshot to an active vm vdi.
If i try to rename it it says no sch VDI, VDI-Snapshot with it's uuid

Danp

@Andi79 Have you tried using xapi-explore-sr to examine how this VDI may be related to other disks?