<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 2 May 2017 at 16:59, Shyam <span dir="ltr"><<a href="mailto:srangana@redhat.com" target="_blank">srangana@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Talur,<br>
<br>
Please wait for this fix before releasing 3.10.2.<br>
<br>
We will take in the change to either prevent add-brick in sharded+distrbuted volumes, or throw a warning and force the use of --force to execute this.<br>
<br></blockquote><div>IIUC, the problem is less the add brick operation and more the rebalance/fix-layout. It is those that need to be prevented (as someone could trigger those without an add-brick).</div><div><br></div><div>Nithya </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Let's get a bug going, and not wait for someone to report it in bugzilla, and also mark it as blocking 3.10.2 release tracker bug.<br>
<br>
Thanks,<br>
Shyam<span class=""><br>
<br>
On 05/02/2017 06:20 AM, Pranith Kumar Karampuri wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
<br>
<br>
On Tue, May 2, 2017 at 9:16 AM, Pranith Kumar Karampuri<br></span><span class="">
<<a href="mailto:pkarampu@redhat.com" target="_blank">pkarampu@redhat.com</a> <mailto:<a href="mailto:pkarampu@redhat.com" target="_blank">pkarampu@redhat.com</a>>> wrote:<br>
<br>
Yeah it is a good idea. I asked him to raise a bug and we can move<br>
forward with it.<br>
<br>
<br>
+Raghavendra/Nitya who can help with the fix.<br>
<br>
<br>
<br>
On Mon, May 1, 2017 at 9:07 PM, Joe Julian <<a href="mailto:joe@julianfamily.org" target="_blank">joe@julianfamily.org</a><br></span><span class="">
<mailto:<a href="mailto:joe@julianfamily.org" target="_blank">joe@julianfamily.org</a>>> wrote:<br>
<br>
<br>
On 04/30/2017 01:13 AM, <a href="mailto:lemonnierk@ulrar.net" target="_blank">lemonnierk@ulrar.net</a><br></span><div><div class="h5">
<mailto:<a href="mailto:lemonnierk@ulrar.net" target="_blank">lemonnierk@ulrar.net</a>> wrote:<br>
<br>
So I was a little but luck. If I has all the hardware<br>
part, probably i<br>
would be firesd after causing data loss by using a<br>
software marked as stable<br>
<br>
Yes, we lost our data last year to this bug, and it wasn't a<br>
test cluster.<br>
We still hear from it from our clients to this day.<br>
<br>
Is known that this feature is causing data loss and<br>
there is no evidence or<br>
no warning in official docs.<br>
<br>
I was (I believe) the first one to run into the bug, it<br>
happens and I knew it<br>
was a risk when installing gluster.<br>
But since then I didn't see any warnings anywhere except<br>
here, I agree<br>
with you that it should be mentionned in big bold letters on<br>
the site.<br>
<br>
Might even be worth adding a warning directly on the cli<br>
when trying to<br>
add bricks if sharding is enabled, to make sure no-one will<br>
destroy a<br>
whole cluster for a known bug.<br>
<br>
<br>
I absolutely agree - or, just disable the ability to add-brick<br>
with sharding enabled. Losing data should never be allowed.<br>
______________________________<wbr>_________________<br>
Gluster-devel mailing list<br></div></div>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a> <mailto:<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.<wbr>org</a>><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/mailm<wbr>an/listinfo/gluster-devel</a><span class=""><br>
<<a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/mail<wbr>man/listinfo/gluster-devel</a>><br>
<br>
<br>
<br>
<br>
--<br>
Pranith<br>
<br>
______________________________<wbr>_________________<br>
Gluster-users mailing list<br></span>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a> <mailto:<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.<wbr>org</a>><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://lists.gluster.org/mailm<wbr>an/listinfo/gluster-users</a><br>
<<a href="http://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://lists.gluster.org/mail<wbr>man/listinfo/gluster-users</a>><br>
<br>
<br>
<br><span class="HOEnZb"><font color="#888888">
<br>
--<br>
Pranith</font></span><span class=""><br>
<br>
<br>
______________________________<wbr>_________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/mailm<wbr>an/listinfo/gluster-devel</a><br>
<br>
</span></blockquote><div class="HOEnZb"><div class="h5">
______________________________<wbr>_________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/mailm<wbr>an/listinfo/gluster-devel</a><br>
</div></div></blockquote></div><br></div></div>