Re: [ovirt-users] Unable to get volume size for domain
El 2018-04-19 08:53, Francesco Romani escribió:
On 04/19/2018 09:44 AM, nico...@devels.es wrote:
Hi,
We're running oVirt 4.1.9 and recently we've experienced a corruption
of a lot of VMs... I tried to investigate the reasons but I simply
can't find an explaination of why this happens.
I'd really appreciate if someone could take a look at these logs and
shed some light on what happened and if this can be fixed somehow,
because these are really a lot of VMs affected... I'm attaching both
engine and SPM's vdsm logs.
These storage domains are all iSCSI-based.
This is pretty frequent on your vdsm logs and alarming:
VolumeGroupSizeError: Volume Group not big enough: ('Not enough free
extents for extending LV
f3bb30a0-4745-4c77-aaca-e5f385905c1e/5c1ad23a-e418-4bb2-86b7-af4b14079224
(free=6, needed=8)',)
The fix depends on how you set up your ISCSI storage
This might be due to a Storage Domain that became 100% full since
yesterday at cca. 16:00.
Could you be more specific on what should I check to know how to fix it?
Thanks.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Unable to get volume size for domain
On 04/19/2018 09:44 AM, nico...@devels.es wrote:
> Hi,
>
> We're running oVirt 4.1.9 and recently we've experienced a corruption
> of a lot of VMs... I tried to investigate the reasons but I simply
> can't find an explaination of why this happens.
>
> I'd really appreciate if someone could take a look at these logs and
> shed some light on what happened and if this can be fixed somehow,
> because these are really a lot of VMs affected... I'm attaching both
> engine and SPM's vdsm logs.
>
> These storage domains are all iSCSI-based.
This is pretty frequent on your vdsm logs and alarming:
VolumeGroupSizeError: Volume Group not big enough: ('Not enough free
extents for extending LV
f3bb30a0-4745-4c77-aaca-e5f385905c1e/5c1ad23a-e418-4bb2-86b7-af4b14079224
(free=6, needed=8)',)
The fix depends on how you set up your ISCSI storage
--
Francesco Romani
Senior SW Eng., Virtualization R&D
Red Hat
IRC: fromani github: @fromanirh
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Unable to get volume size for domain ... after engine upgrade 4.0.4
Hi Bertrand, I solved the problem recovering from old snapshots when possibile (for some VMs i didn't find the LVs on the VG).. I discovered that usually the volume ovirt couldn't get the size, was not resident on the VG. Don't ask me why this happens or when (i'm sure it began on ovirt-3.6 maybe with version 3.6.7, i'm not sure that i had the 3.6.5), i only know that almost all the last snapshots were not resident on the same VG, in some way the machine was running ok up to I shut it down, then no volume anymore. Luckily i could recover the VMs from previous snapshots mounting LVs manually, then with qemu-img convert creating a raw image and the last using dd with netcat to copy on new VMs with the same features (RAM, disk, etc.) of the original VMs. We have about 250 VMs, about 150 have snapshots, I recovered manually about 100 VMs, some from snapshot when clone or export worked, but mostly using the method described. I investigated and discovered that in some way the info on Ovirt-DB were right, but physically on the snapshots were wrong pointing to different VM parent-snapshots or having missing snapshots. If you need some help let me know, but repeat i'm still recovering old VMs, moving them to a new Datacenter. Claudio On 09/11/16 23:19, Bertrand Caplet wrote: Hi Claudio, I'm having the same problem. Did you resolve it ? And how ? Le 20/10/2016 à 17:11, Claudio Soprano a écrit : Hello all, we upgraded the engine (standalone) from 3.6.5 to 4.0.4 for the Backing file too long bug. we upgraded 2 hosts on 10 from 3.6.5 to 4.0.4 too. we tried to shutdown some VMs and now when we try to start them again we get "Unable to get volume size for domain 384f9059-ef2f-4d43-a54f-de71c5d589c8 volume 83ab4406-ea8d-443e-b64b-77b4e1dcb978" Where the domain changes for each VMs we try to start, some VMs have snapshots but one was cloned from a snapshot but has no snapshots itself. Also this cloned VM after the shutdown doesn't start anymore, same error. These VMs don't start neither 3.6.5 or 4.0.4 hosts. I hope in any help because we have about 200 VMs and we don't know if they will start again after a shutdown. Claudio -- /|/ _/ /|/ _/|/ / / | / // / | / // | / / / | / ___/ _// / | / ___/ / | / / / | / // / | / // | / __/ _/ __/ _/ _/ _/ __/ _/ _/ __/ Claudio Sopranophone: (+39)-06-9403.2349/2355 Computing Service fax:(+39)-06-9403.2649 LNF-INFN e-mail: claudio.sopr...@lnf.infn.it Via Enrico Fermi, 40 www:http://www.lnf.infn.it/ I-00044 Frascati, Italy ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Unable to get volume size for domain ... after engine upgrade 4.0.4
Hi Claudio, I'm having the same problem. Did you resolve it ? And how ? Le 20/10/2016 à 17:11, Claudio Soprano a écrit : > Hello all, > > we upgraded the engine (standalone) from 3.6.5 to 4.0.4 for the > Backing file too long bug. > > we upgraded 2 hosts on 10 from 3.6.5 to 4.0.4 too. > > we tried to shutdown some VMs and now when we try to start them again > we get > > "Unable to get volume size for domain > 384f9059-ef2f-4d43-a54f-de71c5d589c8 volume > 83ab4406-ea8d-443e-b64b-77b4e1dcb978" > > Where the domain changes for each VMs we try to start, some VMs have > snapshots but one was cloned from a snapshot but has no snapshots itself. > > Also this cloned VM after the shutdown doesn't start anymore, same error. > > These VMs don't start neither 3.6.5 or 4.0.4 hosts. > > I hope in any help because we have about 200 VMs and we don't know if > they will start again after a shutdown. > > Claudio > > -- CHUNKZ.NET - script kiddie and computer technician Bertrand Caplet, Rennes (FR) Feel free to send encrypted/signed messages Key ID: 6E494EB9 GPG FP: CB1B 664A 9165 98F8 459F 0807 CA35 B76F 6E49 4EB9 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Unable to get volume size for domain ... after engine upgrade 4.0.4
Hello all, we upgraded the engine (standalone) from 3.6.5 to 4.0.4 for the Backing file too long bug. we upgraded 2 hosts on 10 from 3.6.5 to 4.0.4 too. we tried to shutdown some VMs and now when we try to start them again we get "Unable to get volume size for domain 384f9059-ef2f-4d43-a54f-de71c5d589c8 volume 83ab4406-ea8d-443e-b64b-77b4e1dcb978" Where the domain changes for each VMs we try to start, some VMs have snapshots but one was cloned from a snapshot but has no snapshots itself. Also this cloned VM after the shutdown doesn't start anymore, same error. These VMs don't start neither 3.6.5 or 4.0.4 hosts. I hope in any help because we have about 200 VMs and we don't know if they will start again after a shutdown. Claudio -- /|/ _/ /|/ _/|/ / / | / // / | / // | / / / | / ___/ _// / | / ___/ / | / / / | / // / | / // | / __/ _/ __/ _/ _/ _/ __/ _/ _/ __/ Claudio Sopranophone: (+39)-06-9403.2349/2355 Computing Service fax:(+39)-06-9403.2649 LNF-INFN e-mail: claudio.sopr...@lnf.infn.it Via Enrico Fermi, 40 www:http://www.lnf.infn.it/ I-00044 Frascati, Italy ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
