
Hello Andy, Thanks for your reply. I think I understand what's going on there. I think your running the VM in stateless mode, which means that what happened is exactly what should have happened. When you run a VM in stateless mode, What's actually happening is that a snapshot is being taken and the VM runs on this snapshot. When the VM is rebooted the snapshot is deleted (with everything installed on it) and the VM goes back to the previous state (with the previous Active Image). This is the point of the Run stateless feature. If you want the installations to persist, just run the VM, not statelessly. Is it possible that this is what happened? lease let me know if you need any further assistance. Best Regards, Vered ----- Original Message -----
From: "Andy Michielsen" <andy.michielsen@gmail.com> To: "Vered Volansky" <vered@redhat.com> Cc: users@ovirt.org Sent: Thursday, July 10, 2014 8:57:48 AM Subject: Re: [ovirt-users] Disk's locked of VM
Hello Vered,
Sorry for the late reply. You did more than try. With your help I resolved my problem.
I was busy doing my job. This is only a side thing according to my boss but he doesn't know how much time we will safe if we have a decent and easy to use test enviroment to see why something happen in the real world at our customers.
But anyways ...
I have the following setup. One server with the engine on and this one also delivers the storage via nfs. On another server I have only the VDSM setup.
When I say I'm trying to put the disk in stateless mode (off a VM machine) I' mean that I'm trying to install new software on a VM but when I reboot everything is back the way it was before the changed situation of the new software.
Kind regards.
2014-07-06 8:27 GMT+02:00 Vered Volansky < vered@redhat.com > :
Hi Andy,
Happy to (try to) help :)
What do you mean by putting the disks in stateless mode? By server do you mean the storage server, I presume? If so, I can see how this might have caused corruption. Still Would like to be sure what you mean to better understand the issue. Unfortunately, vdsm log was not helpful due to the gap, but the engine log might help out if I knew what operation I was looking for. BTW, Was the vdsm log on the SPM machine? If not, and you do still have it (or a rotation of it), I'd like to take a look and see if we have a bug hiding there.
Thanks, Vered
----- Original Message -----
From: "Andy Michielsen" < andy.michielsen@gmail.com > To: "Vered Volansky" < vered@redhat.com > Cc: users@ovirt.org Sent: Thursday, July 3, 2014 6:03:42 PM Subject: Re: [ovirt-users] Disk's locked of VM
Hello Vered,
We where trying to put the disks i stateless mode and the user was impatient and also started the server. 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.
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.
Kind regards.
2014-07-03 14:57 GMT+02:00 Vered Volansky < vered@redhat.com > :
Sorry, got sent in the middle.
Andy,
What operation did you try to attempt that caused the disks to lock?
You do have a working engine, right? Your'e supposed to be able to see the Disks' GUIDs under the Disks main tab (Id column).
The images GUIDs are available in the DB (images table) and through vdsClient getVolumesList <sdUUID> <spUUID> [imgUUID] imgUUID should be the disk's GUID in the engine. You should be able to get that data from vdsClient as well: getImagesList <sdUUID> relevant sql query: select image_guid, imagestatus from images;
*image status 2 is locked...
The spUUID: Either the datacenter GUID in the engine, or - vdsClient -s 0 getConnectedStoragePoolsList, or in the db: select * from storage_pool;
The StorageDomain's can be retrieved either by DB (bellow) or vdsClient: getStorageDomainsList <spUUID> (from above). sql query: select storage_name, id from storage_domains where storage_pool_id='<spUUID>';
----- Original Message -----
From: "Andy Michielsen" < andy.michielsen@gmail.com > To: "Vered Volansky" < vered@redhat.com > Cc: users@ovirt.org Sent: Thursday, July 3, 2014 3:09:41 PM Subject: Re: [ovirt-users] Disk's locked of VM
Vered,
Where can I find the images GUIDs ?
Kind regards.snapshots'
2014-06-30 17:40 GMT+02:00 Vered Volansky < vered@redhat.com > :
Or better yet, just use:
<oVirtDir>/share/ovirt-engine/dbscripts/unlock_entity.sh
I suppose you have the images GUIDs from engine.
BUT - If the images never got released you might want to get to know what got them into this in the first place. You can send vdsm and engine logs from that period of time if you still got them, and we'll take a look.
Regards, Vered
----- Original Message -----
From: "Vered Volansky" < vered@redhat.com > To: "Andy Michielsen" < andy.michielsen@gmail.com > Cc: users@ovirt.org Sent: Monday, June 30, 2014 6:03:15 PM Subject: Re: [ovirt-users] Disk's locked of VM
From: "Andy Michielsen" < andy.michielsen@gmail.com > To: "Vered Volansky" < vered@redhat.com > Cc: users@ovirt.org Sent: Monday, June 30, 2014 4:57:05 PM Subject: Re: [ovirt-users] Disk's locked of VM
Hello,
How can I connect to my postgress database ? Try this:
----- Original Message ----- psql -d engine -U engine .
This is assuming you're using password authentication. If you aren't please send me your pg_hba.conf settings and we'll go forward from there:
Fedora,RHEL /var/lib/pgsql/data/pg_hba.conf Debian /etc/postgresql/*/main/pg_hba.conf Gentoo /etc/postgresql-*/pg_hba.conf
Kind regards. On Jun 30, 2014 10:10 AM, "Vered Volansky" < vered@redhat.com > wrote:
Hi Andy,
In the DB, try update images set imagestatus = 1 where imagestatus = 2; commit;
Let me know if this helps.
Regards, Vered
----- Original Message -----
From: "Andy Michielsen" < andy.michielsen@gmail.com > To: users@ovirt.org Sent: Friday, June 27, 2014 11:08:47 AM Subject: [ovirt-users] Disk's locked of VM
Hello all,
Does anyone know how I can check if a VM's disk are indeed locked or not. The engine tell's me they are locked but this is now already 16 day's and counting.
I already restarted every server involved but to no avail.
I can not remove, change or start the VM as long as the disks are locked. Can I give a command to check the status of this machine in the CLI enviroment or after connecting to the database and checking a table (Realy don't know how to do this).
Kind regards.
_______________________________________________ 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
_______________________________________________ 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
_______________________________________________ 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