<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">> data-self-heal-algorithm full<br>
<br>
There was a bug in the default algo, at least for VM hosting,<br>
not that long ago. Not sure if it was fixed but I know we were<br>
told here to use full instead, I'm guessing that's why he's using it too.<span class=""><br></span></blockquote><div><br></div><div>Huh, not heard of that. Do you have any useful links I could read up on? My GoogleFu only returned a few posts from 5 years ago...<br><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
> If your images easily fit within the bricks, why do you need sharding in<br>
> the first place? It adds an extra layer of complexity & removes the cool<br>
> feature of having entire files on each brick, making DR & things a lot<br>
> easier.<br>
<br>
</span>Because healing a VM disk without sharding freezes it for the duration of the heal,<br>
possibly hours depending on the size. That's just not acceptable. Unless that's<br>
related to the bug in the heal algo and it's been fixed ? Not sure<br></blockquote><div><br></div></div>I've only been using Gluster since 3.7, last year, but I've not had any of those issues. Looking back, it's had granular locking & healing for a good many versions now.<br><br></div><div class="gmail_extra">Doug<br></div></div>