[SOLVED] NFS Client Fails

Installing and Using OpenWrt
1

Hi,

Pulling my hair out here unfortunately. Trying to mount an NFS export on my OpenWrt box - and have confirmed that I can mount the directory from another machine (so the export is fine). I have also checked, and the server supports nfs 3 and 4, tcp and udp. When I try to mount from the client, I get the following - thoughts?

mount.nfs4: timeout set for Wed Jul 18 20:56:01 2018
mount.nfs4: trying text-based options 'nolock,vers=4.2,addr=192.168.2.64,clientaddr=192.168.2.196'
mount.nfs4: mount(2): Protocol not supported[ 3221.933716] NFS: bad mount option value specified: minorversion=1
mount.nfs4: trying text-based options 'nolock,vers=4,minorversion=1,addr=192.168.2.64,clientaddr=192.168.2.196'
mount.nfs4: mount(2): Invalid argument
mount.nfs4: trying text-based options 'nolock,vers=4,addr=192.168.2.64,clientaddr=192.168.2.196'
mount.nfs4: mount(2): Protocol not supported
mount.nfs4: Protocol not supported

So then, tried to force nfs version 3, as follows,
mount.nfs4 192.168.2.64:/mnt/ProgSSD/openwrt/bin/ /mnt/openwrt -o nolock -v -o nfsvers=3

Then the output is,

mount.nfs4: timeout set for Wed Jul 18 20:58:57 2018
mount.nfs4: trying text-based options 'nolock,nfsvers=3,addr=192.168.2.64'
mount.nfs4: prog 100003, trying vers=3, prot=6
mount.nfs4: trying 192.168.2.64 prog 100003 vers 3 prot TCP port 2049
mount.nfs4: prog 100005, trying vers=3, prot=17
mount.nfs4: trying 192.168.2.64 prog 100005 vers 3 prot UDP port 45203
mount.nfs4: mount(2): Protocol not supported
mount.nfs4: Protocol not supported

Thanks!

2

Do you have all the "moving pieces" in place for NFSv4? Just because you request an earlier version doesn't mean that the server will honor the request. At least as I have my NFS set up, you need kerberos and a user mapper. (No, I don't mount NFSv4 on OpenWRT, so I haven't configured OpenWRT for this.)

3

I admit, not 100% positive - I was assuming that given that this is working on another machine (i.e. can mount the export from ESPRESSObin), then the server was all good. I did enable the 3 items noted as needed for an NFS client, but perhaps there are other moving parts not included - as you say.

Thanks.

4

OK, stumbled on to it! It seems that this page is not quite right,
https://openwrt.org/docs/guide-user/services/nas/nfs.client

=> kmod-fs-nfs is not what is needed, rather kmod-fs-nfs-v4 (or v3). Then it works.

Thanks!

1 Like
5

Might want to prepend to [SOLVED] NFS Client Failed so that others know there is a solution if they face a similar challenge.

6

Done, and thanks!

7

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.