Displaying 3 results from an estimated 3 matches for "gf_resolve_ip".
Did you mean:
gf_resolve_ip6
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 Aug 24
2
Unusual bug in glusterfsd
...:20:34 D [tcp-client.c:77:tcp_connect] client: socket fd = 6
> 2008-08-24 18:20:34 D [tcp-client.c:107:tcp_connect] client: finalized on port `1023'
> 2008-08-24 18:20:34 D [tcp-client.c:128:tcp_connect] client: defaulting remote-port to 6996
> 2008-08-24 18:20:34 D [common-utils.c:179:gf_resolve_ip] resolver: DNS cache not present, freshly probing hostname: 10.0.0.254
> 2008-08-24 18:20:34 D [common-utils.c:204:gf_resolve_ip] resolver: returning IP:10.0.0.254[0] for hostname: 10.0.0.254
> 2008-08-24 18:20:34 D [common-utils.c:212:gf_resolve_ip] resolver: flushing DNS cache
> 2008-08-...
2008 Dec 09
1
File uploaded to webDAV server on GlusterFS AFR - ends up without xattr!
...8-12-09 14:52:56 D [tcp-client.c:77:tcp_connect] client1: socket fd = 6
2008-12-09 14:52:56 D [tcp-client.c:107:tcp_connect] client1: finalized
on port `1021'
2008-12-09 14:52:56 D [tcp-client.c:128:tcp_connect] client1: defaulting
remote-port to 6996
2008-12-09 14:52:56 D [common-utils.c:179:gf_resolve_ip] resolver: DNS
cache not present, freshly probing hostname: 192.168.1.176
2008-12-09 14:52:56 D [common-utils.c:204:gf_resolve_ip] resolver:
returning IP:192.168.1.176[0] for hostname: 192.168.1.176
2008-12-09 14:52:56 D [common-utils.c:212:gf_resolve_ip] resolver:
flushing DNS cache
2008-12-09...