<div dir="ltr">Hi Dan,<div><br></div><div>Yes it is el6. VDSM version currently working without problem vdsm-4.14.11.2-0.el6.x86_64 but for the version vdsm-4.14.17-0.el6.x86_64 it's failing. I used ovirt-engine-3.4.3-1.el6.noarch version.</div><div><br></div><div>Please see attached file <span style="font-family:arial,sans-serif;font-size:13px">vdsm.log and supervdsm.log</span></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Oct 24, 2014 at 6:47 PM, Dan Kenigsberg <span dir="ltr"><<a href="mailto:danken@redhat.com" target="_blank">danken@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 Fri, Oct 24, 2014 at 03:01:40PM +0800, John Michael Mercado wrote:<br>
> Hi All,<br>
><br>
</span>> I need your help. Everytime the vdsm start, the server become *read-only<br>
> file system*. My OS installed in SAN storage.<br>
<br>
Could you share more details about your platfor? Is it el6?<br>
Which vdsm version is running there? Did it work better with a previous<br>
version?<br>
<br>
Do you have anything in /var/log/vdsm/vdsm.log? and supervdsm.log?<br>
<br>
Vdsm may be restoring the host network configuration to some outdated<br>
values that break the connection to you SAN storage.<br>
<span class="HOEnZb"><font color="#888888"><br>
Dan.<br>
</font></span></blockquote></div><br></div></div>