On Tue, Aug 23, 2016 at 6:40 PM, Wolfgang Bucher <wolfgang.bucher@netland-mn.de> wrote:

Hello


in var log messages i get following :


kernel: XFS: possible memory allocation deadlock in kmem_alloc (mode:0x250)


I have this problem on 4 different hosts.


This happens during copying files from network to a thin provisioned disk, no problems with preallocated disks.


What kind of storage are you using? local storage? Even though, it makes little sense to me - the disk is a qcow2 disk, which shouldn't be very fragmented as you might think (qcow2 grows in 64K chunks).
It may grow and grow and grow (until you sparsify it), but that's not going to cause fragmentation. What causes it to be fragmented? Perhaps the internal qcow2 mapping is quite fragmented?
Y.
 


Thanks

Wolfgang


-----Ursprüngliche Nachricht-----
Von: Michal Skrivanek <michal.skrivanek@redhat.com>
Gesendet: Die 23 August 2016 17:11
An: Wolfgang Bucher <wolfgang.bucher@netland-mn.de>
CC: Milan Zamazal <mzamazal@redhat.com>; users@ovirt.org (users@ovirt.org) <users@ovirt.org>
Betreff: Re: [ovirt-users] Problem starting VMs


On 23 Aug 2016, at 11:06, Wolfgang Bucher <wolfgang.bucher@netland-mn.de> wrote:

Thank's

but what do you mean with "initialization is finished”

until it gets from WaitForLaunch to PoweringUp state, effectively until the qemu process properly starts up


sometimes the vm crashes while copying files!

when exactly? Can you describe exactly what you are doing and what is reported as a reason for crash. When exactly does it crash and how?

Thanks,
michal




Wolfgang


-----Ursprüngliche Nachricht-----
Von: Milan Zamazal <mzamazal@redhat.com>
Gesendet: Die 23 August 2016 16:59
An: Wolfgang Bucher <wolfgang.bucher@netland-mn.de>
CC: users@ovirt.org (users@ovirt.org) <users@ovirt.org>
Betreff: Re: AW: Problem starting VMs

 
Wolfgang Bucher <wolfgang.bucher@netland-mn.de> writes:

> the problem is "waiting for launch" takes up to 20 min.
>
>
> I did a lot of tests with some vm's and th problem is:
>
>
> 1.  create a win2012 server
>
> 2. attache a new disk (thin provision)
>
> 3. fill the disk from network share with about 100G
>
> 4. shutdown the vm
>
> 5. reboot host and try starting the vm (takes a lot of time until launch)
>
>
>
> It's because of a high fragmented filessystem 

I see, thank you for the explanation.  In such a case, it may take a lot
of time before all the initialization is finished.

Regards,
Milan
_______________________________________________
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