George Kyriazis
Dabbler
- Joined
- Sep 3, 2013
- Messages
- 42
Hi guys,
I am running 11.2-U2.1, and I am trying to set up NFSv4 on a work environment.
I have clicked "Enable NFSv4" and "NFSv3 ownership model for NFSv4" (note: just trying this now; eventually I would like to set up Kerberos).
Testing a mount from CentOS 7, I am getting the following:
[root@frontend /]# mount -v -t nfs4 10.123.110.11:/mnt/vol/test /mnt/
mount.nfs4: timeout set for Mon Mar 18 21:36:52 2019
mount.nfs4: trying text-based options 'vers=4.1,addr=10.123.110.11,clientaddr=10.123.110.71'
mount.nfs4: mount(2): Protocol not supported
mount.nfs4: trying text-based options 'vers=4.0,addr=10.123.110.11,clientaddr=10.123.110.71'
mount.nfs4: mount(2): Protocol not supported
mount.nfs4: Protocol not supported
[root@frontend /]# mount -v 10.123.110.11:/mnt/vol/test /mnt/
mount.nfs: timeout set for Mon Mar 18 21:36:58 2019
mount.nfs: trying text-based options 'vers=4.1,addr=10.123.110.11,clientaddr=10.123.110.71'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4.0,addr=10.123.110.11,clientaddr=10.123.110.71'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=10.123.110.11'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 10.123.110.11 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 10.123.110.11 prog 100005 vers 3 prot UDP port 945
[root@frontend /]#
and it gets mounted as nfsv3.
On the FreeNAS box, I see:
Mar 18 19:55:15 nas nfsd: can't register svc name
So, it looks like nfsv4 did not get enabled. Any ideas as to what could be wrong?
Thanks!
I am running 11.2-U2.1, and I am trying to set up NFSv4 on a work environment.
I have clicked "Enable NFSv4" and "NFSv3 ownership model for NFSv4" (note: just trying this now; eventually I would like to set up Kerberos).
Testing a mount from CentOS 7, I am getting the following:
[root@frontend /]# mount -v -t nfs4 10.123.110.11:/mnt/vol/test /mnt/
mount.nfs4: timeout set for Mon Mar 18 21:36:52 2019
mount.nfs4: trying text-based options 'vers=4.1,addr=10.123.110.11,clientaddr=10.123.110.71'
mount.nfs4: mount(2): Protocol not supported
mount.nfs4: trying text-based options 'vers=4.0,addr=10.123.110.11,clientaddr=10.123.110.71'
mount.nfs4: mount(2): Protocol not supported
mount.nfs4: Protocol not supported
[root@frontend /]# mount -v 10.123.110.11:/mnt/vol/test /mnt/
mount.nfs: timeout set for Mon Mar 18 21:36:58 2019
mount.nfs: trying text-based options 'vers=4.1,addr=10.123.110.11,clientaddr=10.123.110.71'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4.0,addr=10.123.110.11,clientaddr=10.123.110.71'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=10.123.110.11'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 10.123.110.11 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 10.123.110.11 prog 100005 vers 3 prot UDP port 945
[root@frontend /]#
and it gets mounted as nfsv3.
On the FreeNAS box, I see:
Mar 18 19:55:15 nas nfsd: can't register svc name
So, it looks like nfsv4 did not get enabled. Any ideas as to what could be wrong?
Thanks!