On 24/02/2021 00:27, Jerome Lille wrote:
On Tue, 2021-02-23 at 23:16 +0800, Ed Greshko wrote:
[mountd] debug=all
And then restart the server.
After doing the mount from the client, check the journal for rpc.mountd messages.
Ok, what I got when doing 'mount -v server:/path /path' (i.e. it tried v4 first then succeeded on v3) was
rpc.mountd[20558]: check_default: access by 192.168.1.103 ALLOWED rpc.mountd[20558]: Received NULL request from 192.168.1.103 rpc.mountd[20558]: check_default: access by 192.168.1.103 ALLOWED (cached) rpc.mountd[20558]: Received NULL request from 192.168.1.103 rpc.mountd[20558]: check_default: access by 192.168.1.103 ALLOWED (cached) rpc.mountd[20558]: Received MNT3(/mnt/raid/media) request from 192.168.1.103 rpc.mountd[20558]: authenticated mount request from 192.168.1.103:774 for /mnt/raid/media (/mnt/raid/media) rpc.mountd[20558]: nfsd_fh: inbuf 'desktop 7 \x01005610000000000fe5fb05c7864830a8a9dbe250c2f2ed' rpc.mountd[20558]: nfsd_fh: found 0x55a049addd80 path /mnt/raid/media
That is the output I get when I disable NFSv4 in /etc/nfs.conf.
The other way to disable NFSv4 is to modify /etc/sysconfig/nfs to have the line
# Optional arguments passed to rpc.nfsd. See rpc.nfsd(8) RPCNFSDARGS="--no-nfs-version 4"
You should check that as well.
Bottom line, NFSv4 is set disabled. Those are the 2 ways I know how to do. Maybe there are more?
Could it be that v4 differs from v3 in how it does IP <-> hostname resolution? On the server I have the IP of the client/desktop in the /etc/hosts file and the /etc/exports has only the hostname
No. You see "access by 192.168.1.103 ALLOWE" in all attempts.