Created attachment 1181922 [details] 160718-sn-0.rar is the packets which tcpdump on the glusterfsd' host. Description of problem: You can check below the tcp flow: tcp port 169.254.0.11:1006 <-> 169.254.0.20:49154 1. 169.254.0.20 is the glusterfs server, send the FIN packets to client(169.254.0.11). 2. According to below logs, remote glusterfs client didn't close the fd, why glusterfsd can receive "Broken pipe" error? does it cause glusterfsd close the fd? [2016-07-18 08:38:38.416273] W [socket.c:620:__socket_rwv] 0-tcp.config-server: writev on 169.254.0.11:1006 failed (Broken pipe) [2016-07-18 08:38:38.416280] I [socket.c:2353:socket_event_handler] 0-transport: disconnecting now [2016-07-18 08:38:38.416293] I [server.c:518:server_rpc_notify] 0-config-server: disconnecting connection from LB-1-716-2016/07/18-07:09:40:190843-config-client-0-0-5 [2016-07-18 08:38:38.416302] I [client_t.c:417:gf_client_unref] 0-config-server: Shutting down connection LB-1-716-2016/07/18-07:09:40:190843-config-client-0-0-5 Version-Release number of selected component (if applicable): glusterfs-3.6.9 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Can u please attach the brick logs so that it will help us debug?
Please provide the logs, or clear steps to reproduce the problem. You should be able to reopen the bug when updating it with the needed details. Otherwise you can also send a request to gluster-users
you may close the issue.