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.
Bug 1234598 - Early grace period expiry with NFSv4.1
Summary: Early grace period expiry with NFSv4.1
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: nfs-utils
Version: 7.2
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Steve Dickson
QA Contact: Yongcheng Yang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-22 18:56 UTC by Chuck Lever
Modified: 2015-11-19 04:29 UTC (History)
3 users (show)

Fixed In Version: nfs-utils-1.3.0-0.12.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 04:29:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2196 0 normal SHIPPED_LIVE nfs-utils bug fix update 2015-11-19 08:05:04 UTC

Description Chuck Lever 2015-06-22 18:56:45 UTC 
Description of problem:
The NFS server in upcoming RHEL kernels has the ability to expire the grace period early if there are only NFSv4.1 clients accessing its exports. However, matching support is needed in the nfsdcltrack program that is packaged with nfs-utils.

The support appears in nfs-utils starting around September 19, 2014. I think commit d479ad3adb06 is where it begins. An additional database column is introduced in the nfsdcltrack database to identify clients that have created a session during the server's previous boot instance.

Jeff Layton says:

> The has_session column would be automatically added when the updated
> nfsdcltrack is run for the first time. New kernel+old userspace (and
> vice-versa) should work, but you won't get the benefit of the grace
> period being lifted early.

> Steve, if you backport the nfs-utils patches for this, then I'll be
> happy to take a look if you want me to help review them.


Version-Release number of selected component (if applicable):
nfs-utils-1.3.0-0.8.el7.x86_64 is the latest RHEL 7 version I found.

Expected results:
After these changes are applied, the server should

a) recognize when there are only NFSv4.1 clients that have state to reclaim

b) expire the grace period after the last NFSv4.1 client has finished reclaiming state

c) behave the same (use a fixed 90-second grace period) in all other scenarios
Comment 2 Steve Dickson 2015-06-23 12:39:58 UTC 
commit d479ad3adb0671c48d6fbf3e36bd52a31159c413
Author: Jeff Layton <jlayton>
Date:   Fri Sep 19 11:03:45 2014 -0400

    nfsdcltrack: update schema to v2
Comment 9 J. Bruce Fields 2015-08-06 20:26:29 UTC 
I can reproduce upstream.  I think the NLM grace period is interfering here--this patch helps in the cases I'm testing:

http://marc.info/?l=linux-nfs&m=143889261918791
Comment 10 J. Bruce Fields 2015-08-07 16:13:50 UTC 
Whoops, no, the problem is with my testcase, apologies.

It's sm-notify that's responsible for ending the NLM grace period early, and sm-notify is only run after a full reboot.  (Well, it runs when you restart nfs-server, but there's logic in it to exit immediately if it sees it's already run.)

So the best test is probably to do a full reboot of the server.  In the good cases the client's touch should hang during the reboot, but finish executing soon after nfsd comes back up.  In the bad cases, it should take about another 90 seconds after nfsd comes back up.
Comment 19 errata-xmlrpc 2015-11-19 04:29:54 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2196.html
Note You need to log in before you can comment on or make changes to this bug.