<div dir="ltr">hi,<div><br></div><div>thanks for the reply, *without user interaction.", yes, I still have free space of 26.7TB out of 50TB, i'll try to attach some of the vdsm logs related to this, but is there any chance that this can be cause of network problem and, or system time not sync for each hypervisor and ovirt-engein?</div><div><br></div><div>Thanks Again,</div><div>Sandvik</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Oct 2, 2016 at 6:55 PM, Nir Soffer <span dir="ltr"><<a href="mailto:nsoffer@redhat.com" target="_blank">nsoffer@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Sun, Oct 2, 2016 at 12:06 PM, Sandvik Agustin<br>
<<a href="mailto:agustinsandvik@gmail.com">agustinsandvik@gmail.com</a>> wrote:<br>
> Hi users,<br>
><br>
> I have this problem that sometimes 1 to 3 VM just automatically paused with<br>
> user interaction and getting this error "VM has paused due to no storage<br>
> space error". any inputs from you guys are very appreciated.<br>
<br>
</span>This is expected - when there is no storage space :-)<br>
<br>
The vm is paused when there are some io pending io requests that<br>
could not be fulfilled since you don't have enough space.<br>
<br>
In a real machine the io requests would fail. In a vm, the vm can pause,<br>
you can fix the issue (extend the storage domain), and resume the vm.<br>
<br>
But I guess there is storage space available, otherwise you would<br>
not spend the time sending this mail.<br>
<br>
This can happen when using thin provisioned disks on block storage<br>
(iSCSI, FC). We provision such disk with 1G, and and extend the disk<br>
(add 1G) when it becomes too full (by default, free space < 0.5G).<br>
<br>
If we fail to extend the disk quick enough, the vm will pause before the<br>
extend was completed. Once the extend was completed, we resume<br>
the vm.<br>
<br>
So you may see very short pauses, but they should be rare.<br>
<br>
To understand the issue, we need to inspect vdsm logs from the host<br>
running the vm that paused, showing the timeframe when the vm<br>
was paused.<br>
<br>
You should see this message in the log each time a vm pauses:<br>
<br>
abnormal vm stop device <devname> error ENOSPC<br>
<span class="HOEnZb"><font color="#888888"><br>
Nir<br>
</font></span></blockquote></div><br></div>