Il Gio 11 Apr 2019, 19:12 Sakhi Hadebe <sakhi@sanren.ac.za> ha scritto:

What happened is the engine's root filesystem had filled up. My colleague tried to resize the root lvm. The engine then did not come back. In trying to resolve that he cleaned up the engine and tried to re-install it, no luck in doing that.

That brought down all the VMs. All VMs are down. we trying to move them into one of the standalone kvm host. We have been trying to locate the VM disk images, with no luck.

According to the of the VM xml configuration file.the disk file is /rhev/data-center/mnt/glusterSD/glustermount.goku:_vmstore/9f8ef3f6-53f2-4b02-8a6b-e171b000b420/images/b2b872cd-b468-4f14-ae20-555ed823e84b/76ed4113-51b6-44fd-a3cd-3bd64bf93685

Unfortunately we can find it and the solution on teh forum states that we can only find in the associated logical volume, but i think only when teh vm is running.

The disk images we have been trying to boot up from are the one's we got from the gluster bricks, but the are far small that real images and can't boot

I'd strongly suggest to deploy a new environment over a new storage domain and import there the existing hosts; if you configure the cluster in the new engine for virt+gluster, the engine should be able to automatically detect the gluster volumes there and then you will be able to import the existing storage domains into the new engine.

All the definitions of the VMs are periodically (1h) saved also on a special volume on the storage domain called OVF_STORE so you will find your existing VMs into the new engine and you will be able to start them from there.

On Thu, Apr 11, 2019 at 6:13 PM Simone Tiraboschi <stirabos@redhat.com> wrote:

On Thu, Apr 11, 2019 at 9:46 AM Sakhi Hadebe <sakhi@sanren.ac.za> wrote:
Hi,

We have a situation where the HostedEngine was cleaned up and the VMs are no longer running. Looking at the logs we can see the drive files as:

Do you have any guess on what really happened?
Are you sure that the disks really disappeared?

Please notice that the symlinks under rhev/data-center/mnt/glusterSD/glustermount... are created on the fly only when needed.

Are you sure that your host is correctly connecting the gluster storage domain?

2019-03-26T07:42:46.915838Z qemu-kvm: -drive file=/rhev/data-center/mnt/glusterSD/glustermount.goku:_vmstore/9f8ef3f6-53f2-4b02-8a6b-e171b000b420/images/b2b872cd-b468-4f14-ae20-555ed823e84b/76ed4113-51b6-44fd-a3cd-3bd64bf93685,format=qcow2,if=none,id=drive-ua-b2b872cd-b468-4f14-ae20-555ed823e84b,serial=b2b872cd-b468-4f14-ae20-555ed823e84b,werror=stop,rerror=stop,cache=none,aio=native: 'serial' is deprecated, please use the corresponding option of '-device' instead

I assume this is the disk was writing to before it went down. Trying to list the file gives an error and the file is not there;
ls -l /rhev/data-center/mnt/glusterSD/glustermount.goku:_vmstore/9f8ef3f6-53f2-4b02-8a6b-e171b000b420/images/b2b872cd-b468-4f14-ae20-555ed823e84b/76ed4113-51b6-44fd-a3cd-3bd64bf93685

Is there a way we can recover the VM's disk images ?

NOTE: No HostedEngine backups

--
Regards,

Sakhi Hadebe
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/FPTPLMY4TC4FVYPU7U44SLEVHVD57VOS/

--
Regards,

Sakhi Hadebe
Engineer: South African National Research Network (SANReN)Competency Area, Meraka, CSIR
 
Tel:   +27 12 841 2308
Fax:   +27 12 841 4223
Cell:  +27 71 331 9622
Email: sakhi@sanren.ac.za