Hello, when I reboot one out of the two servers in a replicated setup, the volume turns into read only mode until the first server is back. This is not what I expected and I wonder if I misconfigured anything. The expected behaviour from my point of view is that the volume stays read write and that the rebooting node will catch up again. My setup consists of three servers, two of them hosting the brick, the third one only contributing to the quorom. Thanks for any hint! Nico -------------------------------------------------------------------------------- I mount the volume from fstab with this line: vmhost2-cluster1.place4.ungleich.ch:/cluster1 /var/lib/one/datastores/100 glusterfs defaults,_netdev,backupvolfile-server=vmhost1-cluster1.place4.ungleich.ch 0 0 [19:10:05] vmhost1-cluster1:~# gluster volume info Volume Name: cluster1 Type: Replicate Volume ID: b371ec1f-e01e-49f8-9573-e0d1e74bbd90 Status: Started Number of Bricks: 1 x 2 = 2 Transport-type: tcp Bricks: Brick1: vmhost1-cluster1.place4.ungleich.ch:/home/gluster Brick2: vmhost2-cluster1.place4.ungleich.ch:/home/gluster Options Reconfigured: nfs.disable: 1 cluster.ensure-durability: off server.allow-insecure: on performance.quick-read: off performance.read-ahead: off performance.io-cache: off performance.stat-prefetch: on cluster.eager-lock: enable network.remote-dio: enable cluster.quorum-type: auto cluster.server-quorum-type: server [19:25:15] vmhost1-cluster1:~# gluster peer status Number of Peers: 2 Hostname: entrance.place4.ungleich.ch Uuid: 987e543e-fbc4-497b-9bc9-ae56086d9421 State: Peer in Cluster (Connected) Hostname: 192.168.0.2 Uuid: 688816e1-aa51-450f-9300-979c4e83e33e State: Peer in Cluster (Connected) Other names: 136.243.38.8 -- New PGP key: 659B 0D91 E86E 7E24 FD15 69D0 C729 21A1 293F 2D24 _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
