Replies below: On Fri, 23 Jun 2006, Torsten Boob wrote:
> Hello, > > i have Problems to set up a nfsrdma connection (nfsrdma update 5). > > ./nfsrdmamount -o rdma=192.168.99.1 192.168.99.1:/nfs /mnt/nfs > > has following output on the client. The first message is from the client code... > RPC: xprt_setup_rdma: 192.168.99.1:2049 but these messages are from the server code... > unexpected event received for QP=ffff81013eaaea00, event =4 > svc_rdma_recvfrom: transport ffff81013f54b600 is closing > svc_rdma_recvfrom: transport ffff81013f54b600 is closing > svc_rdma_put: Destroying transport ffff81013f54b600, cm_id=ffff81013f54b400, > sk_flags=54, sk_inuse=0 and these are from the client code. > nfs: RPC call returned error 103 > nfsmount: Software caused connection abort Are you trying to mount to and from the same host? > Using normal nfs with > > mount -t nfs 192.168.99.1:/nfs /mnt/nfs > > results in > > mount: 192.168.99.1:/nfs: can't read superblock It looks like you have a configuration error unrelated to RDMA. If you're looking for documentation on setting up NFS, I'd recommend this: http://nfs.sourceforge.net/nfs-howto/index.html > Same results with openib svn {20060516} > Tested with Debian Sarge and Etch. > > Any ideas ? We've seen the unexpected event received for QP=ffff81013eaaea00, event =4 message once before. There is a timing issue between the NFS-RDMA server and the RDMA stack that we've only seen on IA64 systems to date. What type of hardware are you using? We are working on a fix for this now. _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
