I though that to, but I think is more. When I run: vdsm-tool
dump-volume-chains "sd_id" I get:
image: ad23c0db-1838-4f1f-811b-2b213d3a11cd
- 15259a3b-1065-4fb7-bc3c-04c5f4e14479
status: OK, voltype: INTERNAL, format: COW, legality:
LEGAL, type: SPARSE, capacity: 21474836480, truesize: 6279929856
- 024e1844-c19b-40d8-a2ac-cb4ea6ec34e6
status: OK, voltype: LEAF, format: COW, legality:
ILLEGAL, type: SPARSE, capacity: 21474836480, truesize: 1302528
15259a3b-1065-4fb7-bc3c-04c5f4e14479 is the snapshot.
Am 26.02.22 um 21:50 schrieb Joseph Goldman:
Sounds to me as though it has completed the disk delete underneath
but
it has remained in the database.
I've had similar issues with it also locking the images on the VM and
making me worried it can not be started up should it shut down.
Unfortunately the best fix I've found on a production kit is to try
and simply restore from latest backups as a new VM and delete the old
one. I managed in one or 2 cases to 'clone' the VM to create the new one.
The other solution 'may' be to just delete it from the database, how
to do so cleanly im not sure, but you'd also have to make sure the
disk chain etc is in-tact and matches what is now in the engine
database. It gets really messy really quickly when this kind of thing
happens and has caused me a good amount of stress before :P
------ Original Message ------
From: "Jonathan Baecker" <jonbae77(a)gmail.com>
To: "users" <users(a)ovirt.org>
Sent: 27/02/2022 5:53:38 AM
Subject: [ovirt-users] Deleting Snapshot failed
> Hello everybody,
>
> last night my backup script was not able to finish the backup from a
> VM in the last step of deleting the snapshot. And now I also can not
> delete this snapshot by hand, the message says:
>
> VDSM onode2 command MergeVDS failed: Drive image file could not
> be found: {'driveSpec': {'poolID':
> 'c9baa5d4-3543-11eb-9c0c-00163e33f845', 'volumeID':
> '024e1844-c19b-40d8-a2ac-cb4ea6ec34e6', 'imageID':
> 'ad23c0db-1838-4f1f-811b-2b213d3a11cd', 'domainID':
> '3cf83851-1cc8-4f97-8960-08a60b9e25db'}, 'job':
> '96c7003f-e111-4270-b922-d9b215aaaea2', 'reason': 'Cannot
find
> drive'}
>
> The full log you found in the attachment.
>
> Any idea?
>
> Best regard
>
> Jonathan
>
_______________________________________________
Users mailing list --users(a)ovirt.org
To unsubscribe send an email tousers-leave(a)ovirt.org
Privacy
Statement:https://www.ovirt.org/privacy-policy.html
oVirt Code of
Conduct:https://www.ovirt.org/community/about/community-guidelines/
List
Archives:https://lists.ovirt.org/archives/list/users@ovirt.org/message/TN...