mount - unknown option rdma

Shirish Pargaonkar shirishpargaonkar at gmail.com
Thu Feb 7 23:03:10 EST 2008


On 2/7/08, James Lentini <jlentini at netapp.com> wrote:
>
>
> On Thu, 7 Feb 2008, Shirish Pargaonkar wrote:
>
> > James,
> >
> > I just mailed the data to you.  I can ssh from server to client
> > using ip address assinged to ib interface on the client.
>
> The IP config looks good.
>
> > The mount command fails with rdma as an unknows option, I guess that
> > needs to get fixed to even start going over ib interfaces right?
>
> What changed? After you switched to using nfs-utils-1.1.1, you sent
> this:
>
>  client:~ # /home/shirish/nfs-utils-1.1.1/utils/mount/mount.nfs 1.2.3.131:/ /mnt -i -o rdma,port=2050
>  mount.nfs: Connection timed out
>
> The "connection timed out" error suggests either a server that is not
> listening or a connectivity problem. Since you were able to mount the
> server over TCP, the later seemed more likely.
>

James,

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)


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.

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.

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.


Regards,

Shirish


More information about the NFSv4 mailing list