[Users] Vm's being paused

[Neil]

Thanks for the replies guys,

Looking at my two VM's that have paused so far through the oVirt GUI
the following sizes show under Disks.

VM Reports:
Virtual Size 35GB,  Actual Size 41GB
Looking on the Centos OS side, Disk size is 33G and used is 12G with
19G available (40%) usage.

VM Babbage:
Virtual Size is 40GB, Actual Size 53GB
On the Server 2003 OS side, Disk size is 39.9Gb and used is 16.3G, so
under 50% usage.


Do you see any issues with the above stats?

Then my main Datacenter storage is as follows...

Size: 6887 GB
Available: 1948 GB
Used: 4939 GB
Allocated: 1196 GB
Over Allocation: 61%

Could there be a problem here? I can allocate additional LUNS if you
feel the space isn't correctly allocated.

Apologies for going on about this, but I'm really concerned that
something isn't right and I might have a serious problem if an
important machine locks up.

Thank you and much appreciated.

Regards.

Neil Wilson.












On Tue, Jan 21, 2014 at 7:02 PM, Dafna Ron <dron at redhat.com> wrote:
> the storage space is configured in percentages and not physical size.
> so if 20G is less than 10% (default config) of your storage it will pause
> the vms regardless of how much GB you still have.
> this is configurable though so you can change it to less than 10% if you
> like.
>
> to answer the second question, vm's will not pause on ENOSpace error if they
> run out of space internally but only if the external storage cannot be
> consumed. so only if you run out of space in the storage and and not if vm
> runs out of space in its on fs.
>
>
>
> On 01/21/2014 09:51 AM, Neil wrote:
>>
>> Hi Dan,
>>
>> Sorry, attached is engine.log I've taken out the two sections where
>> each of the VM's were paused.
>>
>> Does the error "VM babbage has paused due to no Storage space error"
>> mean the main storage domain has run out of storage, or that the VM
>> has run out?
>>
>> Both VM's appear to have been running on node01 when they were paused.
>> My vdsm versions are all...
>>
>> vdsm-cli-4.13.0-11.el6.noarch
>> vdsm-python-cpopen-4.13.0-11.el6.x86_64
>> vdsm-xmlrpc-4.13.0-11.el6.noarch
>> vdsm-4.13.0-11.el6.x86_64
>> vdsm-python-4.13.0-11.el6.x86_64
>>
>> I currently have a 61% over allocation ratio on my primary storage
>> domain, with 1948GB available.
>>
>> Thank you.
>>
>> Regards.
>>
>> Neil Wilson.
>>
>>
>> On Tue, Jan 21, 2014 at 11:24 AM, Neil <nwilson123 at gmail.com> wrote:
>>>
>>> Hi Dan,
>>>
>>> Sorry for only coming back to you now.
>>> The VM's are thin provisioned. The Server 2003 VM hasn't run out of
>>> disk space there is about 20Gigs free, and the usage barely grows as
>>> the VM only shares printers. The other VM that paused is also on thin
>>> provisioned disks and also has plenty space, this guest is running
>>> Centos 6.3 64bit and only runs basic reporting.
>>>
>>> After the 2003 guest was rebooted, the network card showed up as
>>> unplugged in ovirt, and we had to remove it, and re-add it again in
>>> order to correct the issue. The Centos VM did not have the same issue.
>>>
>>> I'm concerned that this might happen to a VM that's quite critical,
>>> any thoughts or ideas?
>>>
>>> The only recent changes have been updating from Dreyou 3.2 to the
>>> official Centos repo and updating to 3.3.1-2. Prior to updating I
>>> haven't had this issue.
>>>
>>> Any assistance is greatly appreciated.
>>>
>>> Thank you.
>>>
>>> Regards.
>>>
>>> Neil Wilson.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Sun, Jan 19, 2014 at 8:20 PM, Dan Yasny <dyasny at gmail.com> wrote:
>>>>
>>>> Do you have the VMs on thin provisioned storage or sparse disks?
>>>>
>>>> Pausing happens when the VM has an IO error or runs out of space on the
>>>> storage domain, and it is done intentionally, so that the VM will not
>>>> experience a disk corruption. If you have thin provisioned disks, and
>>>> the VM
>>>> writes to it's disks faster than the disks can grow, this is exactly
>>>> what
>>>> you will see
>>>>
>>>>
>>>> On Sun, Jan 19, 2014 at 10:04 AM, Neil <nwilson123 at gmail.com> wrote:
>>>>>
>>>>> Hi guys,
>>>>>
>>>>> I've had two different Vm's randomly pause this past week and inside
>>>>> ovirt
>>>>> the error received is something like 'vm ran out of storage and was
>>>>> paused'.
>>>>> Resuming the vm's didn't work and I had to force them off and then on
>>>>> which
>>>>> resolved the issue.
>>>>>
>>>>> Has anyone had this issue before?
>>>>>
>>>>> I realise this is very vague so if you could please let me know which
>>>>> logs
>>>>> to send in.
>>>>>
>>>>> Thank you
>>>>>
>>>>> Regards.
>>>>>
>>>>> Neil Wilson
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Users mailing list
>>>>> Users at ovirt.org
>>>>> http://lists.ovirt.org/mailman/listinfo/users
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Users mailing list
>>>> Users at ovirt.org
>>>> http://lists.ovirt.org/mailman/listinfo/users
>
>
>
> --
> Dafna Ron