<div class="gmail_quote">We are testing the glusterfs before recommending them to enterprise clients. We found that the file system always hang after running for about 2 days. after killing the server side process and then restart, everything goes back to normal.<br>
<br> Here is the spec and error logged:<br>GlusterFS version: v2.0.1<br><br>Client volume:<br>volume brick_1<br> type protocol/client<br> option transport-type tcp/client<br> option remote-port 7777 # Non-default port<br>
option remote-host server1<br> option remote-subvolume brick<br>end-volume<br><br>volume brick_2<br> type protocol/client<br> option transport-type tcp/client<br> option remote-port 7777 # Non-default port<br> option remote-host server2<br>
option remote-subvolume brick<br>end-volume<br><br>volume bricks<br> type cluster/distribute<br> subvolumes brick_1 brick_2<br>end-volume<br><br>Error logged on client side through /var/log/glusterfs.log<br>
[2009-05-29 14:58:55] E [client-protocol.c:292:call_bail] brick_1:
bailing out frame LK(28) frame sent = 2009-05-29 14:28:54.
frame-timeout = 1800<br>
[2009-05-29 14:58:55] W [fuse-bridge.c:2284:fuse_setlk_cbk]
glusterfs-fuse: 106850788: ERR => -1 (Transport endpoint is not
connected)<br>
error logged on server <br>
[2009-05-29 14:59:15] E [client-protocol.c:292:call_bail] brick_2: bailing out frame LK(28) frame sent = 2009-05-29 14:29:05. frame-timeout = 1800<br>[2009-05-29 14:59:15] W [fuse-bridge.c:2284:fuse_setlk_cbk] glusterfs-fuse: 106850860: ERR => -1 (Transport endpoint is not connected)<br>
<br>
There is error message logged on server side after 1 hour in /var/log/messages:<br>May 29 16:04:16 server2 winbindd[3649]: [2009/05/29 16:05:16, 0] lib/util_sock.c:write_data(564)<br>May 29 16:04:16 server2 winbindd[3649]: write_data: write failure. Error = Connection reset by peer<br>
May 29 16:04:16 server2 winbindd[3649]: [2009/05/29 16:05:16, 0] libsmb/clientgen.c:write_socket(158)<br>May 29 16:04:16 server2 winbindd[3649]: write_socket: Error writing 104 bytes to socket 18: ERRNO = Connection reset by peer<br>
May 29 16:04:16 server2 winbindd[3649]: [2009/05/29 16:05:16, 0] libsmb/clientgen.c:cli_send_smb(188)<br>May 29 16:04:16 server2 winbindd[3649]: Error writing 104 bytes to client. -1 (Connection reset by peer)<br>May 29 16:04:16 server2 winbindd[3649]: [2009/05/29 16:05:16, 0] libsmb/cliconnect.c:cli_session_setup_spnego(859)<br>
May 29 16:04:16 server2 winbindd[3649]: Kinit failed: Cannot contact any KDC for requested realm<br>
</div><br>