On Tue, May 2, 2017 at 9:16 AM, Pranith Kumar Karampuri <pkara...@redhat.com > wrote:
> Yeah it is a good idea. I asked him to raise a bug and we can move forward > with it. > +Raghavendra/Nitya who can help with the fix. > > On Mon, May 1, 2017 at 9:07 PM, Joe Julian <j...@julianfamily.org> wrote: > >> >> On 04/30/2017 01:13 AM, lemonni...@ulrar.net wrote: >> >>> So I was a little but luck. If I has all the hardware part, probably i >>>> would be firesd after causing data loss by using a software marked as >>>> stable >>>> >>> Yes, we lost our data last year to this bug, and it wasn't a test >>> cluster. >>> We still hear from it from our clients to this day. >>> >>> Is known that this feature is causing data loss and there is no evidence >>>> or >>>> no warning in official docs. >>>> >>>> I was (I believe) the first one to run into the bug, it happens and I >>> knew it >>> was a risk when installing gluster. >>> But since then I didn't see any warnings anywhere except here, I agree >>> with you that it should be mentionned in big bold letters on the site. >>> >>> Might even be worth adding a warning directly on the cli when trying to >>> add bricks if sharding is enabled, to make sure no-one will destroy a >>> whole cluster for a known bug. >>> >> >> I absolutely agree - or, just disable the ability to add-brick with >> sharding enabled. Losing data should never be allowed. >> _______________________________________________ >> Gluster-devel mailing list >> Gluster-devel@gluster.org >> http://lists.gluster.org/mailman/listinfo/gluster-devel >> > > > > -- > Pranith > > _______________________________________________ > Gluster-users mailing list > gluster-us...@gluster.org > http://lists.gluster.org/mailman/listinfo/gluster-users > -- Pranith
_______________________________________________ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel