<html style="direction: rtl;">
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<style type="text/css">body p { margin-bottom: 0cm; margin-top: 0pt; } </style>
</head>
<body style="direction: ltr;"
bidimailui-detected-decoding-type="UTF-8"
smarttemplateinserted="true" bgcolor="#FFFFFF" text="#000000">
<font face="Nazli">We should update both of vdsm and ovirt-engine or
vdsm is enough? I check ovirt el repo and it does not have new
version for vdsm. </font><br>
<div style="direction: ltr;" class="moz-cite-prefix">On 10/12/2013
02:11 AM, Dan Kenigsberg wrote:<br>
</div>
<blockquote style="direction: ltr;"
cite="mid:20131011224100.GE25962@redhat.com" type="cite">
<pre style="direction: ltr;" wrap="">On Sat, Oct 12, 2013 at 12:27:02AM +0330, Mohsen Saeedi wrote:
</pre>
<blockquote style="direction: ltr;" type="cite">
<pre style="direction: ltr;" wrap=""> I have same problem too. I have one node as ovirt engine and as
hypervisor too. I successfully upgrade our engine from 3.1 to 3.2 and then
from 3.2 to 3.3 and everything is ok.
then i upgrade our cluster version to 3.3 and then our datacenter to 3.3.
I increase 1GB on virtual machine with 20GB thin disk and I receive
success message on event and our disk increase to 21GB but after host
reboot, i saw message that contains no bootable disk is available!!!
then i try to install new os on that disk (Centos 6.4 minimal) and
anaconda show the error on screen : No usable disks have found. I think
disk corrupt after resizing.
it was test VM but it's very if occur for real and functional VMs.
</pre>
</blockquote>
<pre style="direction: ltr;" wrap="">
Yes, this is indeed a bad bad bug. It was inadvertantly fixed on the
master branch a while ago. Yesterday, we've backported the fix to
3.3.0.1
<a class="moz-txt-link-freetext" href="http://lists.ovirt.org/pipermail/users/2013-October/017018.html">http://lists.ovirt.org/pipermail/users/2013-October/017018.html</a>
Please avoid trying ovirt-3.3.0's new disk resize feature on file-based storage,
unless you upgrade to vdsm vdsm-4.12.1-4 first.
Dan.
</pre>
</blockquote>
<br>
</body>
</html>