search for: serv1r2

...-------- > > vda /var/lib/libvirt/images/fedora23.qcow2 > > hda - > > > > Thanks for the reply! The original image is still there. Only the 1st and > only top-level snapshot is deleted. > the blockcommit fails though: > [root@vm1 ~]# virsh blockcommit serv1r2 vda --active --pivot > error: block copy still active: disk 'vda' already in active block job What does 'virsh blockjob serv1r2 vda' report? If it's something like this: $ virsh blockjob fedora23 vda Active Block Commit: [100 %] Then you just need to finalize the block jo...

...nstead of --pivot for 'virsh blockcommit' and it will finish after step 2 above. Also one of the cases which would help is that libvirt could actually remove the file after commit, which would avoid the original problem, since the file would still be there. > oot@vm1 ~]# virsh blockjob serv1r2 vda > Active Block Commit: [100 %] > > [root@vm1 ~]# virsh blockjob --pivot serv1r2 vda > > [root@vm1 ~]# > [root@vm1 ~]# ls -l /var/lib/libvirt/images/serv1r2.qcow2 > -rw-r--r--. 1 qemu qemu 54200696832 Jun 30 10:39 /var/lib/libvirt/images/serv1r2.qcow2 > [root@vm1 ~]#...

Hi, Can you try this command: virsh snapshot-delete serv1r2 snap --metadata On Wed, Aug 23, 2017 at 4:41 PM, Doug Hughes <doug.hughes@keystonenap.com> wrote: > I'm not sure how this snapshot got created, but, I cannot delete it, and > its presence prevents me from creating other snapshots. I don't know if it > was created by a co...

..., Aug 23, 2017 at 4:56 PM, Doug Hughes <doug.hughes@keystonenap.com> wrote: > THat did it! Can you esplain what was going on and how that fixed it? > Thanks > > On 8/23/2017 10:50 AM, Sakhi Hadebe wrote: > > Hi, > > Can you try this command: > virsh snapshot-delete serv1r2 snap --metadata > > > > > On Wed, Aug 23, 2017 at 4:41 PM, Doug Hughes <doug.hughes@keystonenap.com> > wrote: > >> I'm not sure how this snapshot got created, but, I cannot delete it, and >> its presence prevents me from creating other snapshots. I don'...

sorry about top post, tablet mail client... brilliant! that did it! Any idea what happened to cause it to partially fail and get into this state? oot@vm1 ~]# virsh blockjob serv1r2 vda Active Block Commit: [100 %] [root@vm1 ~]# virsh blockjob --pivot serv1r2 vda [root@vm1 ~]# [root@vm1 ~]# ls -l /var/lib/libvirt/images/serv1r2.qcow2 -rw-r--r--. 1 qemu qemu 54200696832 Jun 30 10:39 /var/lib/libvirt/images/serv1r2.qcow2 [root@vm1 ~]# date Fri Jun 30 10:39:12 EDT 2017 [root@...

...m blockcommit command!) So now I'm in a state. The domain i still running. but it's running off the -snapshot that is in the xml. I googled around for how to recover a blockcommit from a deleted snapshot, but didn't find anything. (pointers welcome) [root@vm1 images]# virsh domblklist serv1r2 Target Source ------------------------------------------------ vda /var/lib/libvirt/images/serv1r2-snap.qcow2 fda - hdb /var/lib/libvirt/images/virtio-win-0.1.126.iso I can see the size increasing on the deleted file in lsof: qemu-kvm 48994 49033 qemu 97u REG...

...------------------------------------------------ > vda /var/lib/libvirt/images/fedora23.qcow2 > hda - > Thanks for the reply! The original image is still there. Only the 1st and only top-level snapshot is deleted. the blockcommit fails though: [root@vm1 ~]# virsh blockcommit serv1r2 vda --active --pivot error: block copy still active: disk 'vda' already in active block job