gs1:/volume1 /data/nfs glusterfs defaults,_netdev,backupvolfile-server=gs2 0 0
also manually:
sudo mount gs1:/volume1 /data/nfs
I am mounting it with the client on the same machine as the server is. gs2 acts as a failover on the second machine. The bricks are therefore in replication 2 mode on both machines.
How are you mounting it ? For fuse mounts, you need to specify both the servers in your mount command. NFS mounts won't work if the server from which you are trying to mount is offline.On Thu, Aug 27, 2015 at 4:14 AM, Merlin Morgenstern <merlin.morgenstern@xxxxxxxxx> wrote:_______________________________________________I have two gluster servers installed on seperate machines. The function as failover and I do mount on each machine with the coresponding gluster client. This only seems to work if both gluster servers are live.
It seems that something is misconfigured or misunderstood by myself how gluster works.
This is my configuration of the volume:
user@xnode1:~$ sudo mount gs1:/volume1 /data/nfs/ ^Cuser@xnode1:~$ sudo gluster volume info Volume Name: volume1 Type: Replicate Volume ID: 92d9adb8-756b-4138-87a8-23237d21688f Status: Started Number of Bricks: 1 x 2 = 2 Transport-type: tcp Bricks: Brick1: gs1:/data/gluster/brick Brick2: gs2:/data/gluster/brick Options Reconfigured: performance.readdir-ahead: on performance.cache-size: 256MB server.allow-insecure: on performance.io-thread-count: 16 performance.client-io-threads: onBrick1 is on the same site as the running gluster-server.
Why do I need to have Brick2 online? It is configured in replication mode.
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
