The only thing I can think of would be file hard and soft limits, but I am no oVirt pro.
'no free file handlers in pool' that would make sense to me… Donny From: Tiemen Ruiten [mailto:[email protected]] Sent: Tuesday, December 16, 2014 12:40 PM To: Donny Davis Cc: [email protected] Subject: Re: [ovirt-users] ERROR 'no free file handlers in pool' while creating VM from template About 25-30. The nodes are Xeon(R) CPU E5-2650 0 @ 2.00GHz with 16 hyperthreaded cores and 64 GB of RAM each. At the moment I created the VM, processor load on both nodes was less than 1. On 16 December 2014 at 20:29, Donny Davis <[email protected]> wrote: What is the VM load you are running on your servers? -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Tiemen Ruiten Sent: Tuesday, December 16, 2014 12:27 PM To: [email protected] Subject: [ovirt-users] ERROR 'no free file handlers in pool' while creating VM from template Hello, I ran into a nasty problem today when creating a new, cloned VM from a template (one virtual 20 GBdisk) on our two-node oVirt cluster: on the node where I started a VM creation job, load skyrocketed and some VMs stopped responding until and after the job failed. Everything recovered without intervention, but this obviously shouldn't happen. I have attached the relevant vdsm log file. The button to create the VM was pressed around 11:17, the first error in the vdsm log is at 11:23:58. The ISO domain is a gluster volume exposed via NFS, the storage domain for the VM's is also a gluster volume. The underlying filesystem is ZFS. The hypervisor nodes are full CentOS 6 installs. I'm guessing the 'no free file handlers in pool' in the vdsm log file is key here. What can I do to prevent this from happening again? Apart from not creating new VMs of course :) Tiemen -- Tiemen Ruiten Systems Engineer R&D Media
_______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
