I would guess that it's because of the way Gluster manages its replication internally. I'm trying to locate some reference on that topic but right now I can't. Maybe open a bug with RedHat? Thanks, JF On 09/03/15 11:33, Michaël Couren wrote: > > >> >> If set this option to "none", writting on S1 is OK while S2 if rebooting >> but writting to S2 while S1 is rebooting is not possible. > > Edit : stoping the current writting on S2 and restarting it works... > I don't need to do that on S1... > -- Jean-François Le Fillâtre ------------------------------- HPC Systems Administrator LCSB - University of Luxembourg ------------------------------- PGP KeyID 0x134657C6 _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
