[Gluster-users] Problems with Gluster 3.0.4 on Debian Squeeze

[stephen mulcahy]

Hi,

I've just started playing with gluster on Debian.

I created a gluster filesystem with

glusterfs-volgen --name store1 node33:/webstar1 node34:/webstar1

and installed the generated configs to the servers (node33 and node34) 
and restarted glusterfs-server on both.

On my client I then run

glusterfs --debug --volfile-server=node33 /mnt

and immediately get the following errors

+------------------------------------------------------------------------------+
[2010-06-10 16:55:27] D [glusterfsd.c:1382:main] glusterfs: running in 
pid 2695
[2010-06-10 16:55:27] D [write-behind.c:2526:init] writebehind: 
disabling write-behind for first 1 bytes
[2010-06-10 16:55:27] D [read-ahead.c:884:init] readahead: Using 
conf->page_count = 4
[2010-06-10 16:55:27] D [client-protocol.c:6603:init] node34-1: 
defaulting frame-timeout to 30mins
[2010-06-10 16:55:27] D [client-protocol.c:6614:init] node34-1: 
defaulting ping-timeout to 42
[2010-06-10 16:55:27] D [transport.c:123:transport_load] transport: 
attempt to load file /usr/lib/glusterfs/3.0.4/transport/socket.so
[2010-06-10 16:55:27] W [xlator.c:656:validate_xlator_volume_options] 
node34-1: option 'transport.remote-port' is deprecated, preferred is 
'remote-port', continuing with correction
[2010-06-10 16:55:27] D [xlator.c:285:_volume_option_value_validate] 
node34-1: no range check required for 'option remote-port 6996'
[2010-06-10 16:55:27] D [transport.c:123:transport_load] transport: 
attempt to load file /usr/lib/glusterfs/3.0.4/transport/socket.so
[2010-06-10 16:55:27] D [xlator.c:285:_volume_option_value_validate] 
node34-1: no range check required for 'option remote-port 6996'
[2010-06-10 16:55:27] D [client-protocol.c:6603:init] node33-1: 
defaulting frame-timeout to 30mins
[2010-06-10 16:55:27] D [client-protocol.c:6614:init] node33-1: 
defaulting ping-timeout to 42
[2010-06-10 16:55:27] D [transport.c:123:transport_load] transport: 
attempt to load file /usr/lib/glusterfs/3.0.4/transport/socket.so
[2010-06-10 16:55:27] W [xlator.c:656:validate_xlator_volume_options] 
node33-1: option 'transport.remote-port' is deprecated, preferred is 
'remote-port', continuing with correction
[2010-06-10 16:55:27] D [xlator.c:285:_volume_option_value_validate] 
node33-1: no range check required for 'option remote-port 6996'
[2010-06-10 16:55:27] D [transport.c:123:transport_load] transport: 
attempt to load file /usr/lib/glusterfs/3.0.4/transport/socket.so
[2010-06-10 16:55:27] D [xlator.c:285:_volume_option_value_validate] 
node33-1: no range check required for 'option remote-port 6996'
[2010-06-10 16:55:27] D [client-protocol.c:7027:notify] node33-1: got 
GF_EVENT_PARENT_UP, attempting connect on transport
[2010-06-10 16:55:27] D [name.c:155:client_fill_address_family] 
node33-1: address-family not specified, guessing it to be inet/inet6
[2010-06-10 16:55:27] D [client-protocol.c:7027:notify] node33-1: got 
GF_EVENT_PARENT_UP, attempting connect on transport
[2010-06-10 16:55:27] D [name.c:155:client_fill_address_family] 
node33-1: address-family not specified, guessing it to be inet/inet6
[2010-06-10 16:55:27] D [client-protocol.c:7027:notify] node34-1: got 
GF_EVENT_PARENT_UP, attempting connect on transport
[2010-06-10 16:55:27] D [name.c:155:client_fill_address_family] 
node34-1: address-family not specified, guessing it to be inet/inet6
[2010-06-10 16:55:27] D [client-protocol.c:7027:notify] node34-1: got 
GF_EVENT_PARENT_UP, attempting connect on transport
[2010-06-10 16:55:27] D [name.c:155:client_fill_address_family] 
node34-1: address-family not specified, guessing it to be inet/inet6
[2010-06-10 16:55:27] D [client-protocol.c:7027:notify] node33-1: got 
GF_EVENT_PARENT_UP, attempting connect on transport
[2010-06-10 16:55:27] D [client-protocol.c:7027:notify] node33-1: got 
GF_EVENT_PARENT_UP, attempting connect on transport
[2010-06-10 16:55:27] D [client-protocol.c:7027:notify] node34-1: got 
GF_EVENT_PARENT_UP, attempting connect on transport
[2010-06-10 16:55:27] D [client-protocol.c:7027:notify] node34-1: got 
GF_EVENT_PARENT_UP, attempting connect on transport
[2010-06-10 16:55:27] N [glusterfsd.c:1408:main] glusterfs: Successfully 
started
[2010-06-10 16:55:27] D [client-protocol.c:7041:notify] node33-1: got 
GF_EVENT_CHILD_UP
[2010-06-10 16:55:27] D [client-protocol.c:7041:notify] node33-1: got 
GF_EVENT_CHILD_UP
[2010-06-10 16:55:27] D [client-protocol.c:7041:notify] node34-1: got 
GF_EVENT_CHILD_UP
[2010-06-10 16:55:27] D [client-protocol.c:7041:notify] node34-1: got 
GF_EVENT_CHILD_UP
[2010-06-10 16:55:27] D [client-protocol.c:6178:client_setvolume_cbk] 
node34-1: setvolume failed (Stale NFS file handle)
[2010-06-10 16:55:27] D [fuse-bridge.c:3100:fuse_thread_proc] fuse: 
pthread_cond_timedout returned non zero value ret: 0 errno: 0
[2010-06-10 16:55:27] N [client-protocol.c:6246:client_setvolume_cbk] 
node33-1: Connected to 10.141.0.33:6996, attached to remote volume 'brick1'.
[2010-06-10 16:55:27] N [fuse-bridge.c:2950:fuse_init] glusterfs-fuse: 
FUSE inited with protocol versions: glusterfs 7.13 kernel 7.13
[2010-06-10 16:55:27] D [client-protocol.c:6178:client_setvolume_cbk] 
node34-1: setvolume failed (Stale NFS file handle)

So it seems to connect to the node33 server but fails to connect to the 
node34 server.

Any suggestions on where I'm going wrong here?

Thanks,

-stephen
-- 
Stephen Mulcahy, DI2, Digital Enterprise Research Institute,
NUI Galway, IDA Business Park, Lower Dangan, Galway, Ireland
http://di2.deri.ie    http://webstar.deri.ie    http://sindice.com