On 02/09/2016 06:08 AM, Michal Skrivanek wrote:
On 03 Feb 2016, at 10:37, Rik Theys <Rik.Theys@esat.kuleuven.be> wrote:
Hi,
In the mean time I've noticed the following entries in our periodic logcheck output:
Feb 3 09:05:53 orinoco journal: block copy still active: disk 'vda' not ready for pivot yet Feb 3 09:05:53 orinoco journal: vdsm root ERROR Unhandled exception#012Traceback (most recent call last):#012 File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 734, in wrapper#012 return f(*a, **kw)#012 File "/usr/share/vdsm/virt/vm.py", line 5168, in run#012 self.tryPivot()#012 File "/usr/share/vdsm/virt/vm.py", line 5137, in tryPivot#012 ret = self.vm._dom.blockJobAbort(self.drive.name, flags)#012 File "/usr/share/vdsm/virt/virdomain.py", line 68, in f#012 ret = attr(*args, **kwargs)#012 File "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py", line 124, in wrapper#012 ret = f(*args, **kwargs)#012 File "/usr/lib64/python2.7/site-packages/libvirt.py", line 733, in blockJobAbort#012 if ret == -1: raise libvirtError ('virDomainBlockJobAbort() failed', dom=self)#012libvirtError: block copy still active: disk 'vda' not ready for pivot yet
This is from the host running the VM.
Note that this host is not the SPM of the cluster. I always thought all operations on disk volumes happened on the SPM host?
My question still remains:
I can see the snapshot in the "Disk snapshot" tab of the storage. It has a status of "illegal". Is it OK to (try to) remove this snapshot? Will this impact the running VM and/or disk image?
No, it’s not ok to remove it while live merge(apparently) is still ongoing I guess that’s a live merge bug?
Indeed, this is bug 1302215. I wrote a sql script to help with cleanup in this scenario, which you can find attached to the bug along with a description of how to use it[1]. However, Rik, before trying that, would you be able to run the attached script [2] (or just the db query within) and forward the output to me? I'd like to make sure everything looks as it should before modifying the db directly. Thanks, Greg [1] https://bugzilla.redhat.com/show_bug.cgi?id=1302215#c13 (Also note that the engine should be stopped before running this.) [2] Arguments are the ovirt db name, db user, and the name of the vm you were performing live merge on.
Thanks, michal
Regards,
Rik
On 02/03/2016 10:26 AM, Rik Theys wrote:
Hi,
I created a snapshot of a running VM prior to an OS upgrade. The OS upgrade has now been succesful and I would like to remove the snapshot. I've selected the snapshot in the UI and clicked Delete to start the task.
After a few minutes, the task has failed. When I click delete again on the same snapshot, the failed message is returned after a few seconds.
From browsing through the engine log (attached) it seems the snapshot was correctly merged in the first try but something went wrong in the finalizing fase. On retries, the log indicates the snapshot/disk image no longer exists and the removal of the snapshot fails for this reason.
Is there any way to clean up this snapshot?
I can see the snapshot in the "Disk snapshot" tab of the storage. It has a status of "illegal". Is it OK to (try to) remove this snapshot? Will this impact the running VM and/or disk image?
Regards,
Rik
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Rik Theys System Engineer KU Leuven - Dept. Elektrotechniek (ESAT) Kasteelpark Arenberg 10 bus 2440 - B-3001 Leuven-Heverlee +32(0)16/32.11.07 ---------------------------------------------------------------- <<Any errors in spelling, tact or fact are transmission errors>> _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users