Displaying 2 results from an estimated 2 matches for "client_protocol_handshake_reply".
2008 Aug 01
1
file descriptor in bad state
I've just setup a simple gluster storage system on Centos 5.2 x64 w/ gluster
1.3.10
I have three storage bricks and one client
Everytime i run iozone across this setup, i seem to get a bad file
descriptor around the 4k mark.
Any thoughts why? I'm sure more info is wanted, i'm just not sure what else
to include at this point.
thanks
[root at green gluster]# cat
2008 Dec 09
1
File uploaded to webDAV server on GlusterFS AFR - ends up without xattr!
...er:
returning IP:192.168.1.178[0] for hostname: 192.168.1.178
2008-12-09 14:52:56 D [common-utils.c:212:gf_resolve_ip] resolver:
flushing DNS cache
2008-12-09 14:52:56 D [tcp-client.c:161:tcp_connect] client2: connect on
7 in progress (non-blocking)
2008-12-09 14:52:56 D
[client-protocol.c:5103:client_protocol_handshake_reply] client1: reply
frame has callid: 424242
2008-12-09 14:52:56 D
[client-protocol.c:5137:client_protocol_handshake_reply] client1:
SETVOLUME on remote-host succeeded
2008-12-09 14:52:56 D [afr.c:6001:notify] afr1: GF_EVENT_CHILD_UP from
client1
2008-12-09 14:52:56 D [tcp-client.c:205:tcp_connect]...