I have tested the mount to one server and watch the replication to the other server but how do you tell a client to connect to another Brick if the primary has gone down. glusterfs -f /etc/glusterfs/glusterfs.vol /mnt/glusterfs <- Did this method and it would not replicate the files. I do the regular mount and mount -t glusterfs 10.1.2.192:/test-volume /mnt/glusterfs <- this works fine because it connecting directly. /etc/glusterfs/glusterfs.vol <- Client Machine volume test-volume type protocol/client option transport-type tcp option remote-host 10.1.2.62 option remote-subvolume Brick1 end-volume volume test-volume type protocol/client option transport-type tcp option remote-host 10.1.2.192 option remote-subvolume Brick2 end-volume volume replicate type cluster/replicate subvolumes remote1 remote2 end-volume volume writebehind type performance/write-behind option window-size 1MB subvolumes replicate end-volume volume cache type performance/io-cache option cache-size 512MB subvolumes writebehind end-volume -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://gluster.org/pipermail/gluster-users/attachments/20111006/0fc28e0e/attachment-0001.htm>
