I am still tracking the spurious disonnect I get on 3.4.0alpha3. I tracked the origin to the brick. First I get this error in briack log: [2013-04-24 21:51:01.383866] E [event-poll.c:346:event_dispatch_poll_handler] 0-poll: index not found for fd=12 (idx_hint=5) Then the brick sends TCP FIN to the client. In the client, __socket_ssl_readv() returns with 0, which means EOF, and the client log says: 2013-04-24 21:51:01.385768] W [socket.c:1968:__socket_proto_state_machine] 0-gfs33-client-1: reading from socket failed. Error (No message available), peer (1932.0.2.98:49152) [2013-04-24 21:51:01.385824] I [client.c:2097:client_rpc_notify] 0-gfs33-client-1: disconnected [2013-04-24 21:51:01.433699] W [client-rpc-fops.c:1640:client3_3_entrylk_cbk] 0-gfs33-client-1: remote operation failed: Socket is not connected I guess I know need to track event_pool->reg[] usage. Hints appreciated. -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu@xxxxxxxxxx
