More info: on server side, immediately after the mount command from client (10.255.89.5), the log (/usr/local/var/log/glusterfs/usr-local-etc-glusterfs- glusterd.vol.log) says: [2011-11-01 15:24:34.272402] W [socket.c:1494:__socket_proto_state_machine] 0-socket.management: reading from socket failed. Error (Transport endpoint is not connected), peer (10.255.89.5:996) [2011-11-01 15:24:34.272560] W [socket.c:1494:__socket_proto_state_machine] 0-socket.management: reading from socket failed. Error (Transport endpoint is not connected), peer (10.255.89.5:989) (The client mount command simply returned with no error) On the client side, issuing a 'df' command or an 'ls /mnt/gluz' command that would have caused the glusterfs to respond, did not cause any more log messages on the server. The client and server are pingable from each other and can ssh directly to each other with the IP# used for the mounts. -- Harry Mangalam - Research Computing, OIT, Rm 225 MSTB, UC Irvine [ZOT 2225] / 92697 Google Voice Multiplexer: (949) 478-4487 MSTB Lat/Long: (33.642025,-117.844414) (paste into Google Maps) -- This signature has been OCCUPIED! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20111101/2f823bfd/attachment.html>