[openib-general] NFS(v4)-RDMA

[James Lentini]

I see the problem. The mount command's NFSv4 code needs to be updated 
to use the new default NFS-RDMA port. This patch should fix the 
problem.

--- nfsrdmamount/nfsmount.c	2006-11-29 14:19:41.000000000 -0500
+++ nfsrdmamount/nfsmount.c	2007-01-15 10:19:07.406514000 -0500
@@ -1277,7 +1277,7 @@ int nfs4mount(const char *spec, const ch
 		      else
 		       strcpy(nh, inet_ntoa(server_addr.sin_addr));
 
-		    server_addr.sin_port = htons(2049);
+		    server_addr.sin_port = htons(2050);
 		    printf("Doing nfs/rdma mount to %s, mount protocol to %s\n", mh, nh);
     
 #endif 


On Thu, 11 Jan 2007, vishal wrote:

> Hi,
> 
>     NFSv4 does work over TCP..Any suggestions ?
> 
> Thanks
> 
> Vishla
> 
> On Wed, 2007-01-10 at 12:07 -0500, James Lentini wrote:
> > On Wed, 10 Jan 2007, vishal wrote:
> > 
> > > Hi,
> > > 
> > >       I am getting an invalid argument error when I try to mount using
> > > nfs(v4)-rdma. The mounts with nfs(v3)-rdma work fine. Following are the
> > > details:-
> > > 
> > > 1. Command Issued on the client side: -
> > > ./nfsrdmamount -o rdma=10.0.0.2 -t nfs4 10.0.0.2:/ /data
> > > 
> > > 2. /etc/exports on the client side
> > > /data   10.0.0.1(rw,fsid=0,insecure,no_subtree_check,async)
> > > 
> > > 3. Error recieved:- 
> > > nfsmount: Invalid argument
> > > 
> > > 4. From strace:-
> > > 
> > > mount("10.0.0.2:/", "/data", "nfs4", 0, "\1") = -1 EINVAL (Invalid
> > > argument)
> > 
> > Do NFSv4 mounts work over TCP?
> > 
> > If not, make sure you have v4 enabled on the client and server.
>