<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body>
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p>Noted, many thanks </p>
<p><br>
</p>
<div id="Signature"><br>
<div class="ecxmoz-signature">-- <br>
<br>
<font color="#3366ff"><font color="#000000">Respectfully<b><br>
</b><b>Mahdi A. Mahdi</b></font></font><font color="#3366ff"><br>
<br>
</font><font color="#3366ff"></font></div>
</div>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Pranith Kumar Karampuri <pkarampu@redhat.com><br>
<b>Sent:</b> Tuesday, July 11, 2017 6:41:28 AM<br>
<b>To:</b> Mahdi Adnan<br>
<b>Cc:</b> Pavel Szalbot; gluster-users<br>
<b>Subject:</b> Re: [Gluster-users] Upgrading Gluster revision (3.8.12 to 3.8.13) caused underlying VM fs corruption</font>
<div> </div>
</div>
<div>
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Jul 10, 2017 at 10:33 PM, Mahdi Adnan <span dir="ltr">
<<a href="mailto:mahdi.adnan@outlook.com" target="_blank">mahdi.adnan@outlook.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div dir="ltr">
<div id="m_-2215177946570743016x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif">
<p>I upgraded from 3.8.12 to 3.8.13 without issues.</p>
<p>Two replicated volumes with online update, upgraded clients first and followed by servers upgrade, "stop glusterd, pkill gluster*, update gluster*, start glusterd, monitor healing process and logs, after completion proceed to the other node"</p>
</div>
</div>
</div>
</blockquote>
<div>You should first upgrade servers and then clients. New servers can understand old clients, but it is not easy for old servers to understand new clients in case it started doing something new.<br>
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div dir="ltr">
<div id="m_-2215177946570743016x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif">
<p>check gluster logs for more information.</p>
<span class="HOEnZb"><font color="#888888">
<p><br>
</p>
<div id="m_-2215177946570743016x_Signature"><br>
<div class="m_-2215177946570743016x_ecxmoz-signature">-- <br>
<br>
<font color="#3366ff"><font color="#000000">Respectfully<b><br>
</b><b>Mahdi A. Mahdi</b></font></font><font color="#3366ff"><br>
<br>
</font><font color="#3366ff"></font></div>
</div>
</font></span></div>
<span class="HOEnZb"><font color="#888888">
<hr style="display:inline-block;width:98%">
<div id="m_-2215177946570743016x_divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>From:</b>
<a href="mailto:gluster-users-bounces@gluster.org" target="_blank">gluster-users-bounces@gluster.<wbr>org</a> <<a href="mailto:gluster-users-bounces@gluster.org" target="_blank">gluster-users-bounces@<wbr>gluster.org</a>> on behalf of Pavel Szalbot <<a href="mailto:pavel.szalbot@gmail.com" target="_blank">pavel.szalbot@gmail.com</a>><br>
<b>Sent:</b> Monday, July 10, 2017 7:52:10 PM<br>
<b>To:</b> gluster-users<br>
<b>Subject:</b> [Gluster-users] Upgrading Gluster revision (3.8.12 to 3.8.13) caused underlying VM fs corruption</font>
<div> </div>
</div>
</font></span></div>
<div>
<div class="h5"><font size="2"><span style="font-size:10pt">
<div class="m_-2215177946570743016PlainText">Hi,<br>
<br>
is there a recommended way to upgrade Gluster cluster when upgrading<br>
to newer revision? I experienced filesystem corruption on several but<br>
not all VMs (KVM, FUSE) stored on Gluster during Gluster upgrade.<br>
<br>
After upgrading one of two nodes, I checked peer status and volume<br>
heal info, everything seemed fine so I upgraded second node and then<br>
two VMs remounted root as read-only and dmesg contained I/O errors.<br>
<br>
This did not happen in the past while following the same upgrade<br>
procedure. Documentation mentions only upgrades to higher minor<br>
version. Is there a recommended way to upgrade or did I do something<br>
wrong that should be avoided?<br>
<br>
Thanks for any suggestion<br>
Pavel Szalbot<br>
______________________________<wbr>_________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/gluster-users</a><br>
</div>
</span></font></div>
</div>
</div>
<br>
______________________________<wbr>_________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/gluster-users</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
<div class="gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr">Pranith<br>
</div>
</div>
</div>
</div>
</div>
</body>
</html>