CHANGE: http://review.gluster.com/113 (without the proper error code, rpc won't know if transport is successfully) merged in release-3.2 by Anand Avati (avati)

[2011-07-27 14:21:41.898059] D [rpc-transport.c:672:rpc_transport_load] 0-rpc-transport: attempt to load file /usr/local/lib/glusterfs/3.2git/rpc-transport/rdma.so
[2011-07-27 14:21:41.898114] E [rpc-transport.c:676:rpc_transport_load] 0-rpc-transport: /usr/local/lib/glusterfs/3.2git/rpc-transport/rdma.so: cannot open shared object file: No such file 
or directory
[2011-07-27 14:21:41.898129] E [rpc-transport.c:680:rpc_transport_load] 0-rpc-transport: volume 'test2-client-0': transport-type 'rdma' is not valid or not found on this machine
[2011-07-27 14:21:41.898143] W [rpc-clnt.c:921:rpc_clnt_connection_init] 0-test2-client-0: loading of new rpc-transport failed
pending frames:

patchset: git://git.gluster.com/glusterfs.git
signal received: 11
time of crash: 2011-07-27 14:21:41
configuration details:
argp 1
backtrace 1
dlfcn 1
fdatasync 1
libpthread 1
llistxattr 1
setfsid 1
spinlock 1
epoll.h 1
xattr.h 1
st_atim.tv_nsec 1
package-string: glusterfs 3.2git
/lib/libc.so.6(+0x33af0)[0x7fb41b9c0af0]
/usr/local/lib/libgfrpc.so.0(rpcclnt_cbk_program_register+0x1e4)[0x7fb41c355264]
/usr/local/lib/glusterfs/3.2git/xlator/protocol/client.so(client_init_rpc+0x186)[0x7fb4190d8686]
/usr/local/lib/glusterfs/3.2git/xlator/protocol/client.so(init+0xff)[0x7fb4190d87ff]
/usr/local/lib/libglusterfs.so.0(xlator_init+0x58)[0x7fb41c577868]

---
This happens only if the log-level trace is given. If the log level is INFO, the client process is not crashed, but will hung in there for ever.

CHANGE: http://review.gluster.com/114 (without the proper error code, rpc won't know if transport is successfully) merged in release-3.1 by Anand Avati (avati)

Committed to all the branches.

Works fine with mount command directly & mounting using glusterfsd --log-level=TRACE on 3.2 branch with head at 62adb4d1c204104314e8d1d843dc8ca6c498dc55