We have this same issue also once in a while. Most of the times it is solved by just restarting the ovirt engine. If this doesn't work, try to restart your vdsm service. Kind regards 2014-05-26 10:07 GMT+02:00 Maor Lipchuk <mlipchuk(a)redhat.com&gt;: > On 05/19/2014 05:57 PM, Neil wrote: > > Hi Maor, > > > > Sorry for the late reply. > > > > Unfortunately I don't have much in the way of older logs, but can > > confirm that the VM has been shutdown for about 3 months so there > > really shouldn't be any tasks running. > > > > My version is ovirt-engine-3.3.3-2.el6.noarch > > > > I presume running the command won't have any affect on any other VM's > > so it should be safe to do this? > hi Neil, > > The command should not affect other VMs (Make sure to run the command > with "vm_names ='proxy02'"). > > Just to be sure use SELECT before running the command to check that only > one image is returned: > SELECT * FROM images where image_guid = (SELECT image_guid from > all_disks where disk_alias = 'proxy02_Disk0' and vm_names ='proxy02'); > > > > Thank you! > > > > Regards. > > > > Neil Wilson. > > > > > > On Thu, May 15, 2014 at 11:52 AM, Maor Lipchuk <mlipchuk(a)redhat.com&gt; > > wrote: > >> Hi Neil, > >> > >> I have been looking at your logs but it seems that there is no > >> indication of any operation being done on this specific disk. > >> I also see that there are no running tasks in VDSM, so the disk should > >> not be locked. > >> > >> If you have any older engine logs please send them so we can > >> investigate > >> the problem more better. > >> > >> What is the engine version you are running? > >> > >> If you want to unlock the disk, you can run this query in your > >> postgres: > >> UPDATE images set imagestatus = 1 where image_guid = (SELECT image_guid > >> from all_disks where disk_alias = 'proxy02_Disk0' and vm_names > >> ='proxy02'); > >> > >> regards, > >> Maor > >> > >> On 05/14/2014 05:30 PM, Neil wrote: > >>> Hi Maor, > >>> > >>> Attached are the logs, and below is a screenshot of the event log, I > >>> removed the two disks that were attached to the proxy previously which > >>> completed. > >>> > >>> Thank you! > >>> > >>> Regards. > >>> > >>> Neil Wilson. > >>> > >>> > >>> > >>> On Wed, May 14, 2014 at 2:43 PM, Maor Lipchuk <mlipchuk(a)redhat.com&gt; > >>> wrote: > >>>> Hi Neil, > >>>> > >>>> Can u please attach the logs of engine and VDSM. > >>>> What there is in the event log, was there any operation being done on > >>>> the disk before? > >>>> > >>>> regards, > >>>> Maor > >>>> > >>>> On 05/14/2014 03:35 PM, Neil wrote: > >>>>> Hi guys, > >>>>> > >>>>> I'm trying to remove a VM and reclaim the space that the VM was > >>>>> using. > >>>>> This particular VM had a thin provisioned disk attached as well as > >>>>> "fat" provisioned, the "fat" disks I managed to detach, however when > >>>>> I > >>>>> try to remove the VM, it says "The following disks are locked: > >>>>> Please > >>>>> try again in a few minutes. Attached is a screenshot from the GUI > >>>>> side, showing the proxy disk being locked, any ideas? > >>>>> > >>>>> I'm wanting to completely remove the VM and reclaim the space for > >>>>> the > >>>>> datacenter. > >>>>> > >>>>> Thank you. > >>>>> > >>>>> Regards. > >>>>> > >>>>> Neil Wilson > >>>>> > >>>>> > >>>>> > >>>>> _______________________________________________ > >>>>> Users mailing list > >>>>> Users(a)ovirt.org > >>>>> http://lists.ovirt.org/mailman/listinfo/users > >>>>> > >>>> > >>> > >> > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users