On Fri, May 16, 2014 at 12:06 AM, Krishnan Parthasarathi <kparthas@xxxxxxxxxx> wrote: > Which version of gluster are you using? 3.5.0 on CentOS 6.5 x86_64. Sorry I forgot to mention it. Cheers, James > > thanks, > Krish > > ----- Original Message ----- >> Due to some weird automation things, I noticed the following: >> >> Given a cluster of hosts A,B,C,D >> >> It turns out that if you restart glusterd on host B while you are >> running volume create on host A, this can cause host B to be borked. >> This means: glusterd will refuse to start, and the only fix I found >> was to delete the volume data from it, and re-create the volume. Not >> sure if this is useful or not, but reproducing this is pretty easy in >> case this uncovers a code path that isn't working properly. >> >> HTH, >> James >> _______________________________________________ >> Gluster-devel mailing list >> Gluster-devel@xxxxxxxxxxx >> http://supercolony.gluster.org/mailman/listinfo/gluster-devel >> _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-devel
