<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_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>
<p>check gluster logs for more information.</p>
<p><br>
</p>
<div id="x_Signature"><br>
<div class="x_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 tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> gluster-users-bounces@gluster.org <gluster-users-bounces@gluster.org> on behalf of Pavel Szalbot <pavel.szalbot@gmail.com><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>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">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>
_______________________________________________<br>
Gluster-users mailing list<br>
Gluster-users@gluster.org<br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-users">http://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
</div>
</span></font>
</body>
</html>