Hey guys, I am running gluster over infiniband, and I have a couple of questions. We have four servers, each with 1 disk that I am trying to access over infiniband using gluster. The servers look like they start okay, here are the last 10 or so lines of a client log (they are all identical): 2008-10-07 07:18:40 D [spec.y:196:section_sub] parser: child:stripe0->remote1 2008-10-07 07:18:40 D [spec.y:196:section_sub] parser: child:stripe0->remote2 2008-10-07 07:18:40 D [spec.y:196:section_sub] parser: child:stripe0->remote3 2008-10-07 07:18:40 D [spec.y:196:section_sub] parser: child:stripe0->remote4 2008-10-07 07:18:40 D [spec.y:209:section_end] parser: end:stripe0 2008-10-07 07:18:40 D [glusterfs.c:128:fuse_graph] glusterfs: setting option mount-point to /mnt/glusterfs 2008-10-07 07:18:40 D [xlator.c:115:xlator_set_type] xlator: attempt to load file /usr/local/lib/glusterfs/1.3.12/xlator/mount/fuse.so 2008-10-07 07:18:40 E [fuse-bridge.c:2699:init] glusterfs-fuse: fuse_mount failed (Transport endpoint is not connected) 2008-10-07 07:18:40 E [glusterfs.c:547:main] glusterfs: Initializing FUSE failed It says initializing FUSE failed, but lsmod shows fuse is running. Help? Here are my spec files: Server: # file: /etc/glusterfs/glusterfs-server.vol volume brick type storage/posix option directory /data/export end-volume volume server type protocol/server option transport-type ib-verbs/server option auth.ip.brick.allow * subvolumes brick end-volume Client: # file: /etc/glusterfs/glusterfs-client.vol volume remote1 type protocol/client option transport-type ib-verbs/client option remote-host 192.168.1.240 option remote-subvolume brick end-volume volume remote2 type protocol/client option transport-type ib-verbs/client option remote-host 192.168.1.241 option remote-subvolume brick end-volume volume remote3 type protocol/client option transport-type ib-verbs/client option remote-host 192.168.1.244 option remote-subvolume brick end-volume volume remote4 type protocol/client option transport-type ib-verbs/client option remote-host 192.168.1.248 option remote-subvolume brick end-volume volume stripe0 type cluster/stripe option block-size *:1MB subvolumes remote1 remote2 remote3 remote4 end-volume -------------- next part -------------- An HTML attachment was scrubbed... URL: http://zresearch.com/pipermail/gluster-users/attachments/20081007/cac27f25/attachment.htm