What is going on ? NFS 4.2 - Does not mount yet RH 8 does : mount.nfs: mount(2): Protocol not supported

buzzable · February 21, 2024, 5:40pm

I am running some benchmarks on RL
Linux redhat8 4.18.0-348.el8.x86_64 #1 SMP Mon Oct 4 12:17:22 EDT 2021 x86_64 x86_64 x86_64 GNU/Linux

Vs

Linux rocky9 5.14.0-362.13.1.el9_3.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Dec 13 14:07:45 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Simple nfsV4.2 flex files layout and nconnect super speed pNFS -

[root@redhat8 ~]# mount -vvv -t nfs -o nconnect=8 anvilcubepnfs:/testpnfs /mnt/testpnfs
mount.nfs: timeout set for Wed Feb 21 17:38:52 2024
mount.nfs: trying text-based options ‘nconnect=8,vers=4.2,addr=192.168.10.128,clientaddr=192.168.10.204’
Works

now on Super Rockjy
mount.nfs: timeout set for Wed Feb 21 17:40:31 2024
mount.nfs: trying text-based options ‘nconnect=8,vers=4.2,addr=192.168.10.128,clientaddr=192.168.10.199’
mount.nfs: mount(2): Protocol not supported

Are we ever going to get 4.2 into the kernel?

Any ideas?

nazunalika · February 21, 2024, 5:54pm

[root@xmpp01 ~]# mount -vvv -t nfs router.angelsofclockwork.net:/export/test /mnt
mount.nfs: timeout set for Wed Feb 21 10:50:39 2024
mount.nfs: trying text-based options 'vers=4.2,addr=2001:470:1f19:138::1,clientaddr=2001:470:1f19:138::30'
[root@xmpp01 ~]# mount | grep export/test
router.angelsofclockwork.net:/export/test on /mnt type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp6,timeo=600,retrans=2,sec=sys,clientaddr=2001:470:1f19:138::30,local_lock=none,addr=2001:470:1f19:138::1)
[root@xmpp01 ~]# uname -a
Linux xmpp01.angelsofclockwork.net 5.14.0-362.18.1.el9_3.0.1.x86_64 #1 SMP PREEMPT_DYNAMIC Sun Feb 11 13:49:23 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

“4.2” is in the kernel and works as intended in my lab. I would check to make sure you have all the right packages installed. You may also want to verify dmesg, perhaps showmount -e, rpcinfo. DNS may also be a factor, but it’s rare.

iwalker · February 21, 2024, 6:35pm

If firewalld is running, then the ports will also need to be opened to allow incoming NFS connections.

buzzable · February 22, 2024, 4:03am

Thats a great call but no

firewalld.service - firewalld - dynamic firewall daemon
Loaded: loaded (/usr/lib/systemd/system/firewalld.service; disabled; preset: enabled)
Active: inactive (dead)
Docs: man:firewalld(1)

buzzable · February 22, 2024, 4:11am

Thanks for the quick reply 100% firewalld is off and it will mount old school NFS v3 tcp mode. and here are the packages.dnf install nfs*
Last metadata expiration check: 0:00:51 ago on Thu 22 Feb 2024 04:08:22 GMT.
Package nfs-utils-1:2.5.4-20.el9.x86_64 is already installed.
Package nfs-utils-coreos-1:2.5.4-20.el9.x86_64 is already installed.
Package nfs4-acl-tools-0.4.2-2.el9.x86_64 is already installed.
Package nfsv4-client-utils-1:2.5.4-20.el9.x86_64 is already installed.
Dependencies resolved.

buzzable · February 22, 2024, 4:33am

[mark@rocky92 ~]$ sudo mount -vvv -o nfsvers=3 nfs:/volume1/externalnfs /mnt/externalnfs/
mount.nfs: timeout set for Thu Feb 22 04:35:06 2024
mount.nfs: trying text-based options ‘nfsvers=3,addr=192.168.10.100’
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.10.100 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.10.100 prog 100005 vers 3 prot UDP port 892
[mark@rocky92 ~]$ df
Filesystem 1K-blocks Used Available Use% Mounted on
devtmpfs 4096 0 4096 0% /dev
tmpfs 3928380 0 3928380 0% /dev/shm
tmpfs 1571356 9376 1561980 1% /run
/dev/mapper/rl-root 28463104 5901784 22561320 21% /
/dev/sda2 983040 516564 466476 53% /boot
/dev/sda1 613184 7148 606036 2% /boot/efi
tmpfs 785676 52 785624 1% /run/user/42
tmpfs 785676 36 785640 1% /run/user/1000
nfs:/volume1/externalnfs 1019719296 682937728 336781568 67% /mnt/externalnfs

buzzable · February 22, 2024, 4:38am

showmount -e anvilcubepnfs
Export list for anvilcubepnfs:
/ (everyone)
/testpnfs (everyone)

and
sudo mount -vvv anvilcubepnfs:/ /mnt/root/
mount.nfs: timeout set for Thu Feb 22 04:39:36 2024
mount.nfs: trying text-based options ‘vers=4.2,addr=192.168.10.128,clientaddr=192.168.10.213’
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options ‘vers=4,minorversion=1,addr=192.168.10.128,clientaddr=192.168.10.213’
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options ‘vers=4,addr=192.168.10.128,clientaddr=192.168.10.213’
mount.nfs: mount(2): Protocol not supported
mount.nfs: Protocol not supported
[mark@rocky92 ~]$ df
Filesystem 1K-blocks Used Available Use% Mounted on
devtmpfs 4096 0 4096 0% /dev
tmpfs 3928380 0 3928380 0% /dev/shm
tmpfs 1571356 9376 1561980 1% /run
/dev/mapper/rl-root 28463104 5901788 22561316 21% /
/dev/sda2 983040 516564 466476 53% /boot
/dev/sda1 613184 7148 606036 2% /boot/efi
tmpfs 785676 52 785624 1% /run/user/42
tmpfs 785676 36 785640 1% /run/user/1000
nfs:/volume1/externalnfs 1019719296 682937728 336781568 67% /mnt/externalnfs

buzzable · February 22, 2024, 4:43am

nothing in dmesg
[ 36.190758] FS-Cache: Loaded
[ 36.232128] Key type dns_resolver registered
[ 36.314870] NFS: Registering the id_resolver key type
[ 36.314876] Key type id_resolver registered
[ 36.314877] Key type id_legacy registered

buzzable · February 22, 2024, 5:05am

Back on rh all is well…
[root@redhat8 ~]# mount -vvvvv -t nfs -o nconnect=8 anvilcubepnfs:/testpnfs /mnt/testpnfs
mount.nfs: timeout set for Thu Feb 22 05:03:55 2024
mount.nfs: trying text-based options ‘nconnect=8,vers=4.2,addr=192.168.10.128,clientaddr=192.168.10.204’
[root@redhat8 ~]# df
Filesystem 1K-blocks Used Available Use% Mounted on
devtmpfs 900588 0 900588 0% /dev
tmpfs 930088 0 930088 0% /dev/shm
tmpfs 930088 9276 920812 1% /run
tmpfs 930088 0 930088 0% /sys/fs/cgroup
/dev/mapper/rhel_redhat8-root 13420544 4682948 8737596 35% /
/dev/sda2 1038336 256984 781352 25% /boot
/dev/sda1 613184 5896 607288 1% /boot/efi
tmpfs 186016 12 186004 1% /run/user/42
tmpfs 186016 0 186016 0% /run/user/0
anvilcubepnfs:/testpnfs 83870720 19922944 63947776 24% /mnt/testpnfs

buzzable · February 24, 2024, 10:32am

Rebooted swap the NIC driver and WOW… Rocky on pNFS 4.2 Amazing.

This is on Hammerspace Hyperscale NAS… One of the fastest (no client) NAS presentations on the planet… Love it!! No client and all in Rocky Kernal : VERY COOL… FLEX FILES LAYOUT ON ROCKY…

Here is my fstab file

anvilcubepnfs:/ /mnt/root nfs defaults,port=20491,vers=4.2,_netdev,nconnect=8,noauto 0 0

Stats for anvilcubepnfs:/ mounted on /mnt/root:

NFS mount options: rw,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,acregmin=3,acregmax=60,acdirmin=30,acdirmax=60,hard,proto=tcp,nconnect=8,port=20491,timeo=600,retrans=2,sec=sys,clientaddr=192.168.10.199,local_lock=none
NFS mount age: 0:00:17
NFS server capabilities: caps=0xeffbc0ff,wtmult=512,dtsize=1048576,bsize=0,namlen=255
NFSv4 capability flags: bm0=0xffffbfff,bm1=0x4cfffe3e,bm2=0x801,acl=0xf,sessions,pnfs=LAYOUT_FLEX_FILES,lease_time=45,lease_expired=0
NFS security flavor: 1 pseudoflavor: 0

NFS byte counts:
applications read 0 bytes via read(2)
applications wrote 0 bytes via write(2)
applications read 0 bytes via O_DIRECT read(2)
applications wrote 0 bytes via O_DIRECT write(2)
client read 0 bytes via NFS READ
client wrote 0 bytes via NFS WRITE
RPC statistics:
2 RPC requests sent, 2 RPC replies received (0 XIDs not found)
average backlog queue length: 0

system · April 24, 2024, 10:33am

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.