mount - unknown option rdma

[James Lentini]

On Thu, 7 Feb 2008, Shirish Pargaonkar wrote:

> If I use mount command as stated in the document
>  http://nfs-rdma.sourceforge.net/Documents/README
> this is what I get.
> 
> client:~ # mount 1.2.3.131:/ /mnt -i -o rdma,port=2050
> unknown nfs mount option: rdma
>
> client:~ # mount 1.2.3.131:/ /mnt -o rdma,port=2050
> mount.nfs: Unsupported nfs mount option: rdma
>
> 
> client:# /sbin/mount.nfs -V
> mount.nfs (linux nfs-utils 1.1.1)

That's a mistake in the documentation. You should run:

 mount.nfs 1.2.3.131:/ /mnt -i -o rdma,port=2050

> With -i option, /sbin/mount.nfs is not called.  I do not where is the source
> for the binary mount (/bin/mount) and how the message
>   unknown nfs mount option: rdma
> is spit out. I see that message in file nfs4mount.c.
> Not sure how did it figure out that it is nfs type of filesystem that is
> being mounted without specifying -t option, I guess nfs code is
> built in the mount command.

mount can figure it out automatically, but the -i option instructs it 
not to call /sbin/mount.<filesystem> even if it exists. See mount(8) 
for details.

> Without -i mount.nfs is called which spits out the message
>   mount.nfs: Unsupported nfs mount option: rdma
> and the mount.nfs (/sbin/mount.nfs) version is 1.1.1
> 
> So looks like neither /bin/mount not /sbin/mount.nfs recognize rdma option.

What was the output of?

 mount.nfs 1.2.3.131:/ /mnt -i -o rdma,port=2050

> ethernet interfaces ping and ib interfaces ping.  I can ssh from 
> server to client on either interfaces.  So I am not sure it is a 
> connectivity problem.