Hello! Currently trying to mograte from 1.3 to glusterfs-2.0, as it is now stable. When I start node1 I can access glusterfs, but if I start second one, than trouble comes. Before 1.3 version worked fine. this is what i have in logs: ================================================================================ Version : glusterfs 2.0.0 built on May 11 2009 14:44:39 TLA Revision : 7b2e459db65edd302aa12476bc73b3b7a17b1410 Starting Time: 2009-05-11 17:02:55 Command line : /usr/sbin/glusterfsd --volfile=/etc/glusterfs/glusterfs-server.vol --pid-file=/var/run/glusterfsd.pid --log-file=/var/log/glusterfsd.log PID : 15217 System name : Linux Nodename : fun2 Kernel Release : 2.6.25-hardened-r8.install.20081008 Hardware Identifier: x86_64 Given volfile: +------------------------------------------------------------------------------+ 1: # dataspace on this server 2: volume gfs-ds 3: type storage/posix 4: option directory /mnt/glusterfs 5: end-volume 6: 7: volume locks 8: type features/locks 9: option mandatory-locks on 10: subvolumes gfs-ds 11: end-volume 12: 13: # dataspace on other server 14: volume gfs-storage2-ds 15: type protocol/client 16: option transport-type tcp 17: option remote-host 10.0.1.57 18: option remote-subvolume gfs 19: end-volume 20: 21: # sync stuff 22: volume gfs 23: type cluster/afr 24: subvolumes locks gfs-storage2-ds 25: end-volume 26: 27: #volume gfs 28: # type performance/io-threads 29: # option cache-size 64MB 30: # subvolumes gfs-ds-afr 31: #end-volume 32: 33: volume server 34: type protocol/server 35: option transport-type tcp/server 36: subvolumes gfs 37: option auth.addr.gfs.allow 127.0.0.1,10.0.1.5* 38: end-volume +------------------------------------------------------------------------------+ 2009-05-11 17:02:55 N [afr.c:2120:notify] gfs: subvolume locks came up 2009-05-11 17:02:55 N [afr.c:2120:notify] gfs: subvolume locks came up 2009-05-11 17:02:55 N [glusterfsd.c:1152:main] glusterfs: Successfully started 2009-05-11 17:02:55 N [client-protocol.c:6327:client_setvolume_cbk] gfs-storage2-ds: connection and handshake succeeded 2009-05-11 17:02:55 N [afr.c:2120:notify] gfs: subvolume gfs-storage2-ds came up 2009-05-11 17:02:55 N [client-protocol.c:6327:client_setvolume_cbk] gfs-storage2-ds: connection and handshake succeeded 2009-05-11 17:02:55 N [afr.c:2120:notify] gfs: subvolume gfs-storage2-ds came up 2009-05-11 17:02:56 N [server-protocol.c:7502:mop_setvolume] server: accepted client from 10.0.1.57:1023 2009-05-11 17:02:56 E [client-protocol.c:3733:client_lookup] gfs-storage2-ds: LOOKUP 1/thumbs (/thumbs): failed to get remote inode number for parent 2009-05-11 17:02:56 E [client-protocol.c:3733:client_lookup] gfs-storage2-ds: LOOKUP 1/thumbs (/thumbs): failed to get remote inode number for parent 2009-05-11 17:02:56 E [client-protocol.c:3733:client_lookup] gfs-storage2-ds: LOOKUP 1/thumbs (/thumbs): failed to get remote inode number for parent -------------- next part -------------- A non-text attachment was scrubbed... Name: maris.vcf Type: text/x-vcard Size: 206 bytes Desc: not available URL: <http://zresearch.com/pipermail/gluster-users/attachments/20090511/0798d1e3/attachment.vcf>
