
Hi, we have a problem with some VMs which cannot be started anymore due to an illegal disk status of a snapshot. What happend (most likely)? we tried to snapshot those vms some days ago but the storage domain didn't have enough free space left. Yesterday we shut those vms down - and from then on they didn't start anymore. What have I tried so far? 1. Via the web interface I tried to remove the snapshot - didn't work. 2. Searched the internet. Found (among other stuff) this: https://bugzilla.redhat.com/show_bug.cgi?id=1649129 3. via /vdsm-tool dump-volume-chains/ I managed to list those 5 snapshots (see below). The output for one machine was: image: 2d707743-4a9e-40bb-b223-83e3be672dfe - 9ae6ea73-94b4-4588-9a6b-ea7a58ef93c9 status: OK, voltype: INTERNAL, format: RAW, legality: LEGAL, type: PREALLOCATED, capacity: 32212254720, truesize: 32212254720 - f7d2c014-e8f5-4413-bfc5-4aa1426cb1e2 status: ILLEGAL, voltype: LEAF, format: COW, legality: ILLEGAL, type: SPARSE, capacity: 32212254720, truesize: 29073408 So my idea was to follow the said bugzilla thread and update the volume - but I didn't manage to find input for the /job_id/ and /generation/. So my question is: Does anyone have an idea on how to (force) remove a given snapshot via vsdm-{tool|client}? Thanks in advance! Daniel -- Daniel Menzel Geschäftsführer Menzel IT GmbH Charlottenburger Str. 33a 13086 Berlin +49 (0) 30 / 5130 444 - 00 daniel.menzel@menzel-it.net https://menzel-it.net Geschäftsführer: Daniel Menzel, Josefin Menzel Unternehmenssitz: Berlin Handelsregister: Amtsgericht Charlottenburg Handelsregister-Nummer: HRB 149835 B USt-ID: DE 309 226 751

you can use: $ vdsm-client Volume delete (you can use --help to see the params) After this you'll need to remove the corresponding image manually from the database images table, mark the parent image as active, remove the snapshot from the snapshots table and fix the parent snapshot Be sure to backup before trying this On Sun, Dec 13, 2020 at 5:00 PM Daniel Menzel <daniel.menzel@menzel-it.net> wrote:
Hi,
we have a problem with some VMs which cannot be started anymore due to an illegal disk status of a snapshot.
What happend (most likely)? we tried to snapshot those vms some days ago but the storage domain didn't have enough free space left. Yesterday we shut those vms down - and from then on they didn't start anymore.
What have I tried so far?
Via the web interface I tried to remove the snapshot - didn't work. Searched the internet. Found (among other stuff) this: https://bugzilla.redhat.com/show_bug.cgi?id=1649129 via vdsm-tool dump-volume-chains I managed to list those 5 snapshots (see below).
The output for one machine was:
image: 2d707743-4a9e-40bb-b223-83e3be672dfe
- 9ae6ea73-94b4-4588-9a6b-ea7a58ef93c9 status: OK, voltype: INTERNAL, format: RAW, legality: LEGAL, type: PREALLOCATED, capacity: 32212254720, truesize: 32212254720
- f7d2c014-e8f5-4413-bfc5-4aa1426cb1e2 status: ILLEGAL, voltype: LEAF, format: COW, legality: ILLEGAL, type: SPARSE, capacity: 32212254720, truesize: 29073408
So my idea was to follow the said bugzilla thread and update the volume - but I didn't manage to find input for the job_id and generation.
So my question is: Does anyone have an idea on how to (force) remove a given snapshot via vsdm-{tool|client}?
Thanks in advance! Daniel
-- Daniel Menzel Geschäftsführer
Menzel IT GmbH Charlottenburger Str. 33a 13086 Berlin
+49 (0) 30 / 5130 444 - 00 daniel.menzel@menzel-it.net https://menzel-it.net
Geschäftsführer: Daniel Menzel, Josefin Menzel Unternehmenssitz: Berlin Handelsregister: Amtsgericht Charlottenburg Handelsregister-Nummer: HRB 149835 B USt-ID: DE 309 226 751
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/5ZRHPBH6PKWUXS...
participants (2)
-
Benny Zlotnik
-
Daniel Menzel