Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Original we use "NLM_GRACE_PERIOD" to define the NLM Grace-time in RHEL6.
And in RHEL7, this can be done by setting the RPCNFSDARGS in /etc/sysconfig/nfs file.
But I have tried using both of the above methods, it always shows up as "0" when check with "sysctl fs.nfs.nlm_grace_period".
Version-Release number of selected component (if applicable):
RHEL-7.1 with nfs-utils-1.3.0-0.8.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. set NLM time in /etc/sysconfig/nfs, maybe using:
a. echo "NLM_GRACE_PERIOD=30" >>/etc/sysconfig/nfs
b. echo "RPCNFSDARGS='-G 30'" >>/etc/sysconfig/nfs
2. service nfs-config restart
3. service nfs restart
4. sysctl fs.nfs.nlm_grace_period
Actual results:
[root@hp-dl580g7-04 ~]# sysctl fs.nfs.nlm_grace_period
fs.nfs.nlm_grace_period = 0
Expected results:
[root@hp-dl580g7-04 ~]# sysctl fs.nfs.nlm_grace_period
fs.nfs.nlm_grace_period = 30
Additional info:
The NFSv4 grace-time can be set successfully:
[root@hp-dl580g7-04 ~]# cat /proc/fs/nfsd/nfsv4gracetime
30
Note there is a modification adding lockd.conf to set module parameters (bug 1264387) in nfs-utils-1.3.0-0.26.el7
Maybe we should set this parameter in /etc/modprob.d/lockd.conf. If so, need update the testcase/manpage. Will do some more investigation later.
[root@hp-dl385pg8-08 ~]# head /etc/modprobe.d/lockd.conf
#
# Set the NFS lock manager grace period. n is measured in seconds.
#options lockd nlm_grace_period=90
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
#
# Set the TCP port that the NFS lock manager should use.
# port must be a valid TCP port value (1-65535).
#options lockd nlm_tcpport
#
# Set the UDP port that the NFS lock manager should use.
# port must be a valid UDP port value (1-65535).
[root@hp-dl385pg8-08 ~]# rpm -q nfs-utils
nfs-utils-1.3.0-0.26.el7.x86_64
[root@hp-dl385pg8-08 ~]#