Hello, I believe that what you are looking for are the quorum options: http://www.gluster.org/community/documentation/index.php/Gluster_3.2:_Setting_Volume_Options#cluster.quorum-type Thanks JF On 09/03/15 10:52, Micha?l Couren wrote:> Hi, > I built a simple configuration (glusterfs 3.6.2) with only 2 machines. > > First defined a trusted server pool of 2 servers, S1 and S2 : > S1# gluster peer probe S2 > > Then I defined a replicated volume with 2 brocks. S1 has brick1 and S2 brick2 : > S1# gluster volume create test replica 2 transport tcp S1:/gluster/test S2:/gluster/test > > (/gluster are separate xfs volumes on a SAN) > > All options are default except nfs.disable=on > > Mounting at reboot is OK with this /etc/fstab : > 10.0.0.1:/test /test glusterfs defaults,_netdev,backupvolfile-server=10.0.0.2 0 0 > > Problem : If I reboot - or stop S2, volume on S1 is blocked. > But I want to be able to write in /gluster/test/ and expect S2 to sync when its back. > > This uses to function a couple of month ago with an older version of glusterfs > but not anymore now... > > So : What exact options do I need to achieve this ? > > Thanks >-- Jean-Fran?ois Le Fill?tre ------------------------------- HPC Systems Administrator LCSB - University of Luxembourg ------------------------------- PGP KeyID 0x134657C6
----- Le 9 Mar 15, ? 11:05, JF Le Fill?tre jean-francois.lefillatre at uni.lu a ?crit :> Hello, > > I believe that what you are looking for are the quorum options: > > http://www.gluster.org/community/documentation/index.php/Gluster_3.2:_Setting_Volume_Options#cluster.quorum-type > > Thanks > JF >Thank, 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. -- Cordialement / Best regards, Micha?l Couren, ABES, Montpellier, France.