2017-03-10 11:39 GMT+01:00 Cedric Lemarchand <yipikai7@xxxxxxxxx>: > I am still asking myself how such bug could happen on a clustered storage software, where adding bricks is a base feature for scalable solution, like Gluster. Or maybe is it that STM releases are really under tested compared to LTM ones ? Could we states that STM release are really not made for production, or at least really risky ? This is the same i've reported some months ago. I think it's probably the worst thing in gluster. Tons of critical bugs for critial features (that are also the basis features for a storage software) that lead to data loss and still to be merged. This kind of bugs *MUST* be addressed, fixed and released *ASAP*, not after months and months and are still waiting for a review. _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
