autofs NFSv4 problem with SCALE..?

kim.bjoern

Cadet
Joined
Feb 25, 2022
Messages
2
Very excited with the SCALE release - looks very promising.

Currently testing as VM with a few basic NFS shares, I can't connect macOS autofs clients to share:

Code:
macOS Monterey client w. nfs.client.mount.options = vers=4,resvport

xch@10client0 ~ % showmount -e 172.16.100.14
showmount: Cannot retrieve info from host: 172.16.100.14: RPC failed:: RPC: Program/version mismatch; low version = 3, high version = 3

xch@10client0 ~ % ls -la /net/172.16.100.14 
ls: /net/172.16.100.14: Input/output error


Linux client works fine:
Code:
Debian 11 VM


xfl@r320-esxi-deb-22:~$ /usr/sbin/showmount -e 172.16.100.14
Export list for 172.16.100.14:
/mnt/SSD-148GB *
xfl@r320-esxi-deb-22:~$ ls -la /net/172.16.100.14
total 0
drwxr-xr-x 3 root root 0 Feb 25 11:43 .
drwxr-xr-x 3 root root 0 Feb 25 11:43 ..
drwxr-xr-x 3 root root 0 Feb 25 11:43 mnt
xfl@r320-esxi-deb-22:~$


MacOS works fine with a TrueNAS CORE server:
Code:
xch@10client0 ~ % showmount -e 172.16.100.221
Exports list on 172.16.100.221:
/mnt/vd-24G                         Everyone
xch@10client0 ~ % ls -la /net/172.16.100.221
total 6
dr-xr-xr-x  2 root  wheel  1 Feb 25 11:47 .
dr-xr-xr-x  3 root  wheel  2 Feb 25 08:25 ..
dr-xr-xr-x  2 root  wheel  1 Feb 25 11:47 mnt
xch@10client0 ~ %


Any ideas to fix - or debug..?
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
Could it be that the NFS service hasn't had NFSv4 enabled?

Seems your mapping is asking for it and the error seems to be saying max version is 3.

The default for the service is 4 not enabled.
 

kim.bjoern

Cadet
Joined
Feb 25, 2022
Messages
2
Could it be that the NFS service hasn't had NFSv4 enabled?

Seems your mapping is asking for it and the error seems to be saying max version is 3.

The default for the service is 4 not enabled.
Thanks @sretalla - but no.

Screenshot 2022-02-25 at 13.10.10.png


NFSv4 is on, and the unix client connects to v4.x:

Code:
xfl@r320-esxi-deb-22:~$ /usr/sbin/showmount -e 172.16.100.14
Export list for 172.16.100.14:
/mnt/SSD-148GB *
xfl@r320-esxi-deb-22:~$ ls -la /net/172.16.100.14/mnt/
total 1
drwxr-xr-x 3 root root 0 Feb 25 13:07 .
drwxr-xr-x 3 root root 0 Feb 25 13:07 ..
drwxr-xr-x 4 root root 4 Feb 25 12:08 SSD-148GB
xfl@r320-esxi-deb-22:~$ /usr/sbin/nfsstat -m
/net/172.16.100.14/mnt/SSD-148GB from 172.16.100.14:/mnt/SSD-148GB
 Flags:    rw,nosuid,nodev,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=172.16.100.22,local_lock=none,addr=172.16.100.14


...and the MacOS client can connect to NFSv4 services (on a Debian 11):

Code:
xch@10client0 ~ % /usr/bin/showmount -e 172.16.100.22
Exports list on 172.16.100.22:
/tmp                                *
xch@10client0 ~ % ls -la /net/172.16.100.22         
total 12
dr-xr-xr-x   3 root  wheel     2 Feb 25 13:04 .
dr-xr-xr-x   3 root  wheel     2 Feb 25 08:25 ..
drwxrwxrwt  17 root  wheel  4096 Feb 25 13:07 tmp
xch@10client0 ~ % /usr/bin/nfsstat -m               
/System/Volumes/Data/net/172.16.100.22/tmp from 172.16.100.22:/tmp
  -- Original mount options:
     General mount flags: 0x500418 nodev,nosuid,automounted,quarantine,nobrowse
     NFS parameters: vers=4,resvport
     File system locations:
       /tmp @ 172.16.100.22 (172.16.100.22)
  -- Current mount parameters:
     General mount flags: 0x4500418 nodev,nosuid,automounted,quarantine,nobrowse,multilabel
     NFS parameters: vers=4.0,tcp,port=2049,hard,nointr,resvport,callback,negnamecache,nonamedattr,noacl,noaclonly,locks,noquota,rsize=32768,wsize=32768,readahead=16,dsize=32768,rdirplus,nodumbtimer,timeo=10,maxgroups=16,acregmin=5,acregmax=60,acdirmin=5,acdirmax=60,nomutejukebox,noephemeral,nonfc,sec=sys
     File system locations:
       /tmp @ 172.16.100.22 (172.16.100.22)
     Status flags: 0x0

xch@10client0 ~ % /usr/bin/showmount -e 172.16.100.14
showmount: Cannot retrieve info from host: 172.16.100.14: RPC failed:: RPC: Program/version mismatch; low version = 3, high version = 3
 
Top