-
Bug
-
Resolution: Done
-
Undefined
-
None
-
rhel-10.0
-
No
-
None
-
rhel-fs
-
2
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
What were you trying to do that didn't work?
In /etc/nfs.conf setting "vers4.2=no"will turn off the version 4.2 but after that even though I have cleared that setting, the version 4.2 won't come back automatically:
[root@yoyang-rhel-100-202503056 ~]# vi /etc/nfs.conf
[root@yoyang-rhel-100-202503056 ~]# cat /etc/nfs.conf
[nfsd]
vers4.2=n
[root@yoyang-rhel-100-202503056 ~]# systemctl restart nfs-server
[root@yoyang-rhel-100-202503056 ~]# cat /proc/fs/nfsd/versions
+3 +4 +4.1 -4.2
[root@yoyang-rhel-100-202503056 ~]# vi /etc/nfs.conf
[root@yoyang-rhel-100-202503056 ~]# cat /etc/nfs.conf
[nfsd]
vers4.1=n
[root@yoyang-rhel-100-202503056 ~]# systemctl restart nfs-server
[root@yoyang-rhel-100-202503056 ~]# cat /proc/fs/nfsd/versions
+3 +4 -4.1 -4.2
^^^^
[root@yoyang-rhel-100-202503056 ~]# vi /etc/nfs.conf
[root@yoyang-rhel-100-202503056 ~]# cat /etc/nfs.conf
[nfsd]
vers4.0=n
[root@yoyang-rhel-100-202503056 ~]# systemctl restart nfs-server
[root@yoyang-rhel-100-202503056 ~]# cat /proc/fs/nfsd/versions
+3 -4 -4.0 -4.1 -4.2
^^^^^^^^^^^
[root@yoyang-rhel-100-202503056 ~]# rpm -q kernel nfs-utils
kernel-6.12.0-55.2.1.el10_0.x86_64
nfs-utils-2.8.2-3.el10.x86_64
[root@yoyang-rhel-100-202503056 ~]#
The workaround is to set them back explicitly:
[root@yoyang-rhel-100-202503056 ~]# vi /etc/nfs.conf [root@yoyang-rhel-100-202503056 ~]# cat /etc/nfs.conf [nfsd] vers4=y [root@yoyang-rhel-100-202503056 ~]# systemctl restart nfs-server [root@yoyang-rhel-100-202503056 ~]# cat /proc/fs/nfsd/versions +3 +4 +4.1 +4.2 [root@yoyang-rhel-100-202503056 ~]#
Will check which is the first break version later.
What is the impact of this issue to you?
Please provide the package NVR for which the bug is seen:
How reproducible is this bug?:
Steps to reproduce
Expected results
Actual results
- relates to
-
-
- Release Pending
-
