GlusterFS 3.1.3 [192.168.0.1]# gluster volume create test replica 2 transport tcp 192.168.0.1:/gluster 192.168.0.2:/gluster [192.168.0.1]# gluster volume start test [192.168.0.3]# mount -t glusterfs 192.168.0.2:/test /mnt/test Now share /mnt/test with SAMBA and start copying a bunch of files. During data transfer unplug network cable from 192.168.0.1. Data transfer hangs as long as the SAMBA client (being WinXP or smbclient) timeouts and aborts data transfer. I think this could easily be unacceptable in a production environment. I guessed the fuse-mounting client was able to load balancing between gluster peers. Raf
