<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
<div class="moz-cite-prefix">On 7/12/2015 9:03 PM, Udo Giacomozzi
wrote:<br>
</div>
<blockquote cite="mid:56656779.5000707@indunet.it" type="cite">All
VMs were running on machine #1 - the two other machines (#2 and
#3) were <b class="moz-txt-star"><span class="moz-txt-tag">*</span>idle<span
class="moz-txt-tag">*</span></b>.
<br>
Gluster was fully operating (no healing) when I rebooted machine
#2.
<br>
For other reasons I had to reboot machines #2 and #3 a few times,
but since all VMs were running on machine #1 and nothing on the
other machines was accessing Gluster files, I was confident that
this wouldn't disturb Gluster.
<br>
But anyway this means that I rebootet Gluster nodes during a
healing process.
<br>
<br>
After a few minutes, Gluster files began showing corruption - up
to the point that the qcow2 files became unreadable and all VMs
stopped working.
<br>
</blockquote>
<br>
Udo, it occurs to me that if your VM's were running on #2 & #3
and you live migrated them to #1 prior to rebooting #2/3, then you
would indeed rapidly get progressive VM corruption.<br>
<br>
However it wouldn't be due to the heal process, but rather the live
migration with "performance.stat-prefetch" on. This always leads to
qcow2 files becoming corrupted and unusable.<br>
<br>
<pre class="moz-signature" cols="72">--
Lindsay Mathieson</pre>
</body>
</html>