hi R.C.,
The network ping timeout for glusterfs is around 45 seconds. If samba client ping timeout is lesser than this then the connection could be aborted. Could you check if the same happens after setting the ping-timeout to something lesser than the samba client.
example: gluster volume set test network.ping-timeout 10
Pranith.
----- Original Message -----
From: "R.C." <milanraf at gmail.com>
To: gluster-users at gluster.org
Sent: Sunday, March 20, 2011 4:27:35 AM
Subject: Unreachable peer stops data transfer on volume
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
_______________________________________________
Gluster-users mailing list
Gluster-users at gluster.org
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
