<div dir="ltr"><div><div><div>Hello Vered,<br><br></div>We where trying to put the disks i stateless mode and the user was impatient and also started the server.<br>I have changed the lock status now but the machine was broken. I 'm already creating a new VM as these are test machines and I don't care about the data in these VM's.<br>
</div><br></div><div>Thank you very much for your assistance so far. I 'm curious still what happened though so if you have questions I will give additional info if needed.<br></div><div><br></div>Kind regards.<br></div>
<div class="gmail_extra"><br><br><div class="gmail_quote">2014-07-03 14:57 GMT+02:00 Vered Volansky <span dir="ltr"><<a href="mailto:vered@redhat.com" target="_blank">vered@redhat.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Sorry, got sent in the middle.<br>
<br>
Andy,<br>
<br>
What operation did you try to attempt that caused the disks to lock?<br>
<br>
You do have a working engine, right?<br>
Your'e supposed to be able to see the Disks' GUIDs under the Disks main tab (Id column).<br>
<br>
The images GUIDs are available in the DB (images table) and through vdsClient getVolumesList <sdUUID> <spUUID> [imgUUID]<br>
imgUUID should be the disk's GUID in the engine.<br>
You should be able to get that data from vdsClient as well:<br>
getImagesList <sdUUID><br>
relevant sql query:<br>
select image_guid, imagestatus from images;<br>
<br>
*image status 2 is locked...<br>
<br>
The spUUID:<br>
Either the datacenter GUID in the engine, or -<br>
vdsClient -s 0 getConnectedStoragePoolsList, or in the db:<br>
select * from storage_pool;<br>
<br>
The StorageDomain's can be retrieved either by DB (bellow) or vdsClient:<br>
getStorageDomainsList <spUUID> (from above).<br>
sql query:<br>
select storage_name, id from storage_domains where storage_pool_id='<spUUID>';<br>
<div class=""><br>
----- Original Message -----<br>
> From: "Andy Michielsen" <<a href="mailto:andy.michielsen@gmail.com">andy.michielsen@gmail.com</a>><br>
> To: "Vered Volansky" <<a href="mailto:vered@redhat.com">vered@redhat.com</a>><br>
> Cc: <a href="mailto:users@ovirt.org">users@ovirt.org</a><br>
</div><div class="">> Sent: Thursday, July 3, 2014 3:09:41 PM<br>
> Subject: Re: [ovirt-users] Disk's locked of VM<br>
><br>
</div><div class="">> Vered,<br>
><br>
> Where can I find the images GUIDs ?<br>
><br>
</div>> Kind regards.snapshots'<br>
<div class="HOEnZb"><div class="h5">><br>
><br>
> 2014-06-30 17:40 GMT+02:00 Vered Volansky < <a href="mailto:vered@redhat.com">vered@redhat.com</a> > :<br>
><br>
><br>
> Or better yet, just use:<br>
><br>
> >> <oVirtDir>/share/ovirt-engine/dbscripts/unlock_entity.sh<br>
><br>
> I suppose you have the images GUIDs from engine.<br>
><br>
> BUT -<br>
> If the images never got released you might want to get to know what got them<br>
> into this in the first place.<br>
> You can send vdsm and engine logs from that period of time if you still got<br>
> them, and we'll take a look.<br>
><br>
> Regards,<br>
> Vered<br>
><br>
> ----- Original Message -----<br>
> > From: "Vered Volansky" < <a href="mailto:vered@redhat.com">vered@redhat.com</a> ><br>
> > To: "Andy Michielsen" < <a href="mailto:andy.michielsen@gmail.com">andy.michielsen@gmail.com</a> ><br>
> > Cc: <a href="mailto:users@ovirt.org">users@ovirt.org</a><br>
> > Sent: Monday, June 30, 2014 6:03:15 PM<br>
> > Subject: Re: [ovirt-users] Disk's locked of VM<br>
> ><br>
> ><br>
> ><br>
> > ----- Original Message -----<br>
> > > From: "Andy Michielsen" < <a href="mailto:andy.michielsen@gmail.com">andy.michielsen@gmail.com</a> ><br>
> > > To: "Vered Volansky" < <a href="mailto:vered@redhat.com">vered@redhat.com</a> ><br>
> > > Cc: <a href="mailto:users@ovirt.org">users@ovirt.org</a><br>
> > > Sent: Monday, June 30, 2014 4:57:05 PM<br>
> > > Subject: Re: [ovirt-users] Disk's locked of VM<br>
> > ><br>
> > ><br>
> > ><br>
> > > Hello,<br>
> > ><br>
> > > How can I connect to my postgress database ?<br>
> > Try this:<br>
> > psql -d engine -U engine .<br>
> ><br>
> > This is assuming you're using password authentication.<br>
> > If you aren't please send me your pg_hba.conf settings and we'll go forward<br>
> > from there:<br>
> ><br>
> > Fedora,RHEL /var/lib/pgsql/data/pg_hba.conf<br>
> > Debian /etc/postgresql/*/main/pg_hba.conf<br>
> > Gentoo /etc/postgresql-*/pg_hba.conf<br>
> ><br>
> > ><br>
> > > Kind regards.<br>
> > > On Jun 30, 2014 10:10 AM, "Vered Volansky" < <a href="mailto:vered@redhat.com">vered@redhat.com</a> > wrote:<br>
> > ><br>
> > ><br>
> > > Hi Andy,<br>
> > ><br>
> > > In the DB, try<br>
> > > update images set imagestatus = 1 where imagestatus = 2;<br>
> > > commit;<br>
> > ><br>
> > > Let me know if this helps.<br>
> > ><br>
> > > Regards,<br>
> > > Vered<br>
> > ><br>
> > > ----- Original Message -----<br>
> > > > From: "Andy Michielsen" < <a href="mailto:andy.michielsen@gmail.com">andy.michielsen@gmail.com</a> ><br>
> > > > To: <a href="mailto:users@ovirt.org">users@ovirt.org</a><br>
> > > > Sent: Friday, June 27, 2014 11:08:47 AM<br>
> > > > Subject: [ovirt-users] Disk's locked of VM<br>
> > > ><br>
> > > > Hello all,<br>
> > > ><br>
> > > > Does anyone know how I can check if a VM's disk are indeed locked or<br>
> > > > not.<br>
> > > > The<br>
> > > > engine tell's me they are locked but this is now already 16 day's and<br>
> > > > counting.<br>
> > > ><br>
> > > > I already restarted every server involved but to no avail.<br>
> > > ><br>
> > > > I can not remove, change or start the VM as long as the disks are<br>
> > > > locked.<br>
> > > > Can<br>
> > > > I give a command to check the status of this machine in the CLI<br>
> > > > enviroment<br>
> > > > or after connecting to the database and checking a table (Realy don't<br>
> > > > know<br>
> > > > how to do this).<br>
> > > ><br>
> > > > Kind regards.<br>
> > > ><br>
> > > > _______________________________________________<br>
> > > > Users mailing list<br>
> > > > <a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
> > > > <a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
> > > ><br>
> > ><br>
> > > _______________________________________________<br>
> > > Users mailing list<br>
> > > <a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
> > > <a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
> > ><br>
> > _______________________________________________<br>
> > Users mailing list<br>
> > <a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
> > <a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
> ><br>
><br>
><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
><br>
</div></div></blockquote></div><br></div>