Melvin, Just fixed it in patch-841. Thanks! Krishna On Thu, Jan 8, 2009 at 2:38 PM, Melvin Wong <melvin.wong@xxxxxxxxx> wrote: > Hi Krishna, > I am getting this error "Transport endpoint is not connected" on one of > my clients when I try to use the configuration below. Any ideas what > could have gone wrong? Thank you. > > > 2009-01-08 16:54:33 E [ha.c:4301:notify] glusterfs-ha: GF_EVENT_CHILD_UP > from cluster > 2009-01-08 16:54:40 D [client-protocol.c:5699:client_protocol_reconnect] > cluster2: breaking reconnect chain > 2009-01-08 16:54:40 D [client-protocol.c:5699:client_protocol_reconnect] > cluster: breaking reconnect chain > 2009-01-08 16:54:52 D [inode.c:280:__inode_activate] fuse/inode: > activating inode(1), lru=0/0 active=1 purge=0 > 2009-01-08 16:54:52 D [fuse-bridge.c:1944:fuse_statfs] glusterfs-fuse: > 2: STATFS > 2009-01-08 16:54:52 E [ha-helpers.c:243:_ha_next_active_child_for_ctx] > glusterfs-ha: failed to get the state from inode->ctx > 2009-01-08 16:54:52 E [ha.c:3289:ha_statfs] glusterfs-ha: no active > subvolume > 2009-01-08 16:54:52 E [fuse-bridge.c:1912:fuse_statfs_cbk] > glusterfs-fuse: 2: ERR => -1 (Transport endpoint is not connected) >
