Description of problem: The file /proc/fs/nfsd/nfsv4recoverydir is not readable on RHEL5. I found this problem while running the kernel/fs/proc/proc01 LTP test on 2.6.18-141, although it applies to previous kernels too. # uname -a Linux myhost 2.6.18-141.el5 #1 SMP Fri Apr 24 17:46:35 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux # service nfs start . . . # cat /proc/fs/nfsd/nfsv4recoverydir cat: /proc/fs/nfsd/nfsv4recoverydir: Invalid argument On Fedora 11 beta it works correctly: # service nfs start . . . # cat /proc/fs/nfsd/nfsv4recoverydir /var/lib/nfs/v4recovery I believe this is the upstream fix: http://linux-nfs.org/pipermail/nfsv4/2008-June/008709.html
Created attachment 343301 [details] RHEL5 backport of upstream patch Jeff, here's a backport of the patch that seems to fix the issue. I only pulled the chunks that are needed to read nfsv4recoverydir. Please let me know if I missed anything.
Patch looks reasonable to me -- if you've tested it and feel comfortable with it, go ahead and post it to RHKL. You might as well own the BZ too, fwiw...
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
in kernel-2.6.18-149.el5 You can download this test kernel from http://people.redhat.com/dzickus/el5 Please do NOT transition this bugzilla state to VERIFIED until our QE team has sent specific instructions indicating when to do so. However feel free to provide a comment indicating that this fix has been verified.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2009-1243.html