Agreed.
I will run the same test on an actual vm setup one of these days and
see if I manage to recreate the issue (after I have completed some
of my long pending tasks). Meanwhile if any of you find a consistent simpler
test case to hit the issue, feel free to reply on this thread. At least I had no successI will run the same test on an actual vm setup one of these days and
see if I manage to recreate the issue (after I have completed some
of my long pending tasks). Meanwhile if any of you find a consistent simpler
in recreating the bug in a non-VM-store setup.
On Mon, Oct 17, 2016 at 12:50 PM, Gandalf Corvotempesta <gandalf.corvotempesta@xxxxxxxxx> wrote:
Il 14 ott 2016 17:37, "David Gossage" <dgossage@xxxxxxxxxxxxxxxxxx> ha scritto:
>
> 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.
>I think that the issue wrote in these emails must be addressed in some way.
It's really bad that adding bricks to a cluster lead to data corruption as adding bricks is a standard administration taskI hope that the issue will be detected and fixed asap.
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
