<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Arial,Helvetica,sans-serif">
<p>I first encountered this bug about a year ago, and lost more than 100 VM.</p>
<p>Sharding is essential to VM datastores and i think Gluster is't that useful without this feature for VMs.</p>
<p>I appreciate all the hard work that the developers putting on this bug, but i think a warning in CLI or something would be really helpful for Gluster users until the fix is ready.</p>
<p></p>
<p><br>
</p>
<div id="x_Signature"><br>
<div class="x_ecxmoz-signature">-- <br>
<br>
<font color="#3366ff"><font color="#000000">Respectfully<b><br>
</b><b>Mahdi A. Mahdi</b></font></font><font color="#3366ff"><br>
<br>
</font><font color="#3366ff"></font></div>
</div>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> gluster-users-bounces@gluster.org <gluster-users-bounces@gluster.org> on behalf of Joe Julian <joe@julianfamily.org><br>
<b>Sent:</b> Monday, May 1, 2017 6:37:00 PM<br>
<b>To:</b> gluster-users@gluster.org; Gluster Devel<br>
<b>Subject:</b> [Gluster-users] Don't allow data loss via add-brick (was Re: Add single server)</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText"><br>
On 04/30/2017 01:13 AM, lemonnierk@ulrar.net wrote:<br>
>> So I was a little but luck. If I has all the hardware part, probably i<br>
>> would be firesd after causing data loss by using a software marked as stable<br>
> Yes, we lost our data last year to this bug, and it wasn't a 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 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 happens and I knew it<br>
> was a risk when installing gluster.<br>
> But since then I didn't see any warnings anywhere except here, I agree<br>
> with you that it should be mentionned in big bold letters on the site.<br>
><br>
> Might even be worth adding a warning directly on the cli when trying to<br>
> add bricks if sharding is enabled, to make sure no-one will destroy a<br>
> whole cluster for a known bug.<br>
<br>
I absolutely agree - or, just disable the ability to add-brick with <br>
sharding enabled. Losing data should never be allowed.<br>
_______________________________________________<br>
Gluster-users mailing list<br>
Gluster-users@gluster.org<br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-users">http://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
</div>
</span></font>
</body>
</html>