[libvirt-users] block commit failed at 100%

[Ishmael Tsoaela]

Hi Dominique,

I have attempted an abort and commit normally works fine the second time,
this is how I normally manually fix my backups but this time around it's
showing me flames.



On Mon, Jun 27, 2016 at 12:13 PM, Dominique Ramaekers <
dominique.ramaekers at cometal.be> wrote:

> You can abort the commit with ‘virsh blockjob vm /mnt/… --abort’ and retry
> the commit again. In my experience the second time, the blockjob always
> completes successfully.
>
>
>
> I’ve changed completely from using file images to logical volumes. I get
> the feeling, using external snapshots with file images isn’t really stable
> on the commit part. I never can reproduce a stuck commit, so I haven’t
> filed a bug rapport for this behavior…
>
>
>
>
>
>
>
> *Van:* libvirt-users-bounces at redhat.com [mailto:
> libvirt-users-bounces at redhat.com] *Namens *Ishmael Tsoaela
> *Verzonden:* maandag 27 juni 2016 11:56
> *Aan:* libvirt-users at redhat.com
> *Onderwerp:* [libvirt-users] block commit failed at 100%
>
>
>
> Hi All,
>
>
>
> I am new to libvirt and would appreciated some assistance with libvirt
> backups.
>
>
>
> I am backing up some VM and coming accross and issue where "Block commit"
> does not completely finish, causing libvirt to write to snapshot:
>
>
>
>
>
> root at xxx:~# virsh blockjob vm
> /mnt/diskimage-backups/vm.snap-201606210230.qcow2  --info
>
> Active Block Commit: [100 %]
>
>
>
> The state does not change, is the anyway around this ?
>
>
>
> libvirtd (libvirt) 1.3.4
>
> QEMU emulator version 2.3.0
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20160627/c2190bcc/attachment.htm>