<div dir="ltr"><div><div>Agreed.<br>I will run the same test on an actual vm setup one of these days and<br>see if I manage to recreate the issue (after I have completed some<br>of my long pending tasks). Meanwhile if any of you find a consistent simpler<br></div>test case to hit the issue, feel free to reply on this thread. At least I had no success<br></div><div>in recreating the bug in a non-VM-store setup.<br></div><div><br></div>-Krutika<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Oct 17, 2016 at 12:50 PM, Gandalf Corvotempesta <span dir="ltr"><<a href="mailto:gandalf.corvotempesta@gmail.com" target="_blank">gandalf.corvotempesta@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><p dir="ltr">Il 14 ott 2016 17:37, "David Gossage" <<a href="mailto:dgossage@carouselchecks.com" target="_blank">dgossage@carouselchecks.com</a>> ha scritto:<br>
><br>
> Sorry to resurrect an old email but did any resolution occur for this or a cause found? I just see this as a potential task I may need to also run through some day and if their are pitfalls to watch for would be good to know.<br>
></p>
</span><p dir="ltr">I think that the issue wrote in these emails must be addressed in some way.<br>
It's really bad that adding bricks to a cluster lead to data corruption as adding bricks is a standard administration task</p>
<p dir="ltr">I hope that the issue will be detected and fixed asap.</p>
<br>______________________________<wbr>_________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://www.gluster.org/<wbr>mailman/listinfo/gluster-users</a><br></blockquote></div><br></div>