NFS4 firmware 3.8.1

[corky]

Unable to mount nfs4

NAS is TS-869 with firmware version: 3.8.1 Build 20121205 on a
Client is Linux Mint 13

I have tried various mount parameters. An example is given below

Code: Select all

mount -t nfs -v  192.168.0.33:/homefolders /home -o nfsvers=4,proto=tcp
mount.nfs: timeout set for Sat Feb  9 18:06:43 2013
mount.nfs: trying text-based options 'nfsvers=4,proto=tcp,addr=192.168.0.33,clientaddr=192.168.0.127'
mount.nfs: mount(2): Protocol not supported
mount.nfs: Protocol not supported

Confirmed with ps that nfs/rpc is running on the NAS

Code: Select all

[~] # ps -e  | grep rpc
  517 admin           SW< [rpciod]
10060 admin       544 S   grep rpc 
11761 admin        96 S   /usr/sbin/rpc.rquotad 
11764 admin      1096 S   /usr/sbin/rpc.statd 
11939 admin      1836 S   /usr/sbin/rpc.mountd -F 
12018 admin      1092 S   /usr/sbin/rpc.statd 
[~] # ps -e  | grep nfs
  546 admin           SW< [nfsiod]
10086 admin       548 S   grep nfs 
11615 admin           SW< [nfsd4]
11616 admin           SW< [nfsd4_callbacks]
11617 admin           SW  [nfsd]
11618 admin           SW  [nfsd]
11619 admin           SW  [nfsd]
11620 admin           SW  [nfsd]
11621 admin           SW  [nfsd]
11622 admin           SW  [nfsd]
11623 admin           SW  [nfsd]
11624 admin           SW  [nfsd]

kernel messages on the NAS

Code: Select all

[~] # dmesg | grep nfs | tail -n 4
[340224.036243] svc: 192.168.0.127, port=698: unknown version (4 for prog 100003, nfsd)
[340370.821851] svc: 192.168.0.127, port=801: unknown version (4 for prog 100003, nfsd)
[340416.404002] svc: 192.168.0.127, port=699: unknown version (4 for prog 100003, nfsd)
[340425.259450] svc: 192.168.0.127, port=687: unknown version (4 for prog 100003, nfsd)

If /home is mounted with nfs3 there are read/write problems with applications being unable to access settings. i would like to see if nfs4 fixes this - how can I enable nfs4 on my NAS?

[schumaku]

NFSv4 is not supported ... once enabled (unsupported: # /sbin/setcfg NFS Enable_V4 TRUE ), the nfsd4 is up and does work basically with pure RPC-based security.

[WalterJ]

Using Enable_V4 also seems to be doing the following:

• Create a /share/NFS folder which is world-exported as common root NFSv4 namespace.
• all the TurboNAS shares are bind-mounted under /share/NFS and are individually re-mountable by NFSv4 clients from there
• default mount options (as specified in /etc/config/nfssetting are interpreted no more (or differenty at least) by QNAP's NFSv4 server.

Can we get some official stance from QNAP as to technical details of their unofficial NFSv4 implementation please?

Besides, is this never going to become officially supported in future firmware?

[schumaku]

Can we get some official stance from QNAP as to technical details of their unofficial NFSv4 implementation please?

No, that's why I state it's not supported...

Besides, is this never going to become officially supported in future firmware?

Send a crystal ball, 5000 US $, and I will try to read it