[SOLVED] mount nfs4 share from openmediavault issue

[k-123]

got a strange issue while mount nfs share from omv. both PVE and OMV has been upgraded to latest version.

nfs options rw,subtree_check,insecure,no_root_squash,anonuid=100,anongid=100 , nfs client has all pve node's ip address included, even try whole lan subnets.

what should I do to make further test or find more useful logs? thanks.

1. created nfs-pve nfs share in omv 6
2. according to omv docs, pve should use /nfs-pve as mount point for nfs4
   https://docs.openmediavault.org/en/6.x/administration/services/nfs.html#clients
3. pve in vm (3 in a cluster, as my test env) can mount the nfs share in version 4.2 (in cli and gui both sucess)
   

   root@test-pve1:~# mount -vv -t nfs4 172.16.0.31:/nfs-pve testmount.nfs4: timeout set for Sun Mar 12 20:56:20 2023
   mount.nfs4: trying text-based options 'vers=4.2,addr=172.16.0.31,clientaddr=172.16.10.11'

4. in physical pve host (5 in a cluster), can only mount above share as nfs3. not 4 or 4.2 (v4/4.2 failed in cli and gui)
   

   root@pve-5:~# mount -vv -t nfs4 172.16.0.31:/nfs-pve testmount.nfs4: timeout set for Sun Mar 12 20:58:19 2023
   mount.nfs4: trying text-based options 'vers=4.2,addr=172.16.0.31,clientaddr=172.16.2.5'
   mount.nfs4: mount(2): No such file or directory
   mount.nfs4: trying text-based options 'addr=172.16.0.31'
   mount.nfs4: prog 100003, trying vers=3, prot=6
   mount.nfs4: trying 172.16.0.31 prog 100003 vers 3 prot TCP port 2049
   mount.nfs4: prog 100005, trying vers=3, prot=17
   mount.nfs4: trying 172.16.0.31 prog 100005 vers 3 prot UDP port 55062
   mount.nfs4: mount(2): Permission denied
   mount.nfs4: access denied by server while mounting 172.16.0.31:/nfs-pve

   logs of omv
   

   Mar 12 20:46:56 nfs-1 rpc.mountd[19916]: refused mount request from 172.16.2.5 for /nfs-pve (/): not exportedMar 12 20:56:20 nfs-1 rpc.mountd[19916]: refused mount request from 172.16.2.5 for /nfs-pve (/): not exported

5. physical pve can mount above nfs share in v3
   

   root@pve-5:~# mount -vv 172.16.0.31:/export/nfs-pve testmount.nfs: timeout set for Sun Mar 12 21:10:52 2023
   mount.nfs: trying text-based options 'vers=4.2,addr=172.16.0.31,clientaddr=172.16.2.5'
   mount.nfs: mount(2): No such file or directory
   mount.nfs: trying text-based options 'addr=172.16.0.31'
   mount.nfs: prog 100003, trying vers=3, prot=6
   mount.nfs: trying 172.16.0.31 prog 100003 vers 3 prot TCP port 2049
   mount.nfs: prog 100005, trying vers=3, prot=17
   mount.nfs: trying 172.16.0.31 prog 100005 vers 3 prot UDP port 55062
   root@pve-5:~# ls test
   images

 

[k-123]

if anyone have similar issue, use separate (only subnet of you pve cluster) nfs share profile, nfs 4.2 will work.