<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 19/05/2016 12:17 AM, Lindsay
Mathieson wrote:<br>
</div>
<blockquote
cite="mid:774623fa-88c1-cb1c-8d1e-d842879074fe@gmail.com"
type="cite">One thought - since the VM's are active while the
brick is removed/re-added, could it be the shards that are written
while the brick is added that are the reverse healing shards?</blockquote>
<br>
<p>I tested by:</p>
<p>- removing brick 3</p>
<p>- erasing brick 3<br>
</p>
<p>- closing down all VM's <br>
</p>
<p>- adding new brick 3</p>
<p>- waiting until heal number reached its max and started
decreasing</p>
<p> There were no reverse heals</p>
<p>- Started the VM's backup. No real issues there though one showed
IO errors, presumably due to shards being locked as they were
healed. <br>
</p>
<p>- VM's started ok, no reverse heals were noted and eventually
Brick 3 was fully healed. The VM's do not appear to be corrupted.</p>
<p><br>
</p>
<p>So it would appear the problem is adding a brick while the volume
is being written to.</p>
<p><br>
</p>
<p>Cheers,<br>
</p>
<pre class="moz-signature" cols="72">--
Lindsay Mathieson</pre>
</body>
</html>