We disabled the NFS FS-Cache code in the kernel configs in RHEL5.3 and "nerfed" the mount option. At the time we had a lively discussion on RHKL about whether to go ahead and back out all of the fscache code. The time before 5.3 shipped was growing short however, and we opted to take a small, simple patch to just disable the mount option and then plan to commit the larger patch to remove fscache from RHEL5 altogether in 5.4. That latter part never happened. So, now a fair bit of the NFS code in RHEL5 is divergent from upstream code. That makes backporting difficult. I'm now bumping up against that since I'm looking at backporting a fair number of upstream patches to fix some writeback problems (see bug 441730 and bug 516490). Cloning the original bug for us to reconsider ripping out the fscache code for 5.7.
*** Bug 481680 has been marked as a duplicate of this bug. ***
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.
Patch(es) available in kernel-2.6.18-248.el5 Detailed testing feedback is always welcomed.
verified the patch is being applied in kernel-2.6.18-264.el5 and according to comment #6, nfs works normally, pls check the below regression test results: https://errata.devel.redhat.com/errata/show/10670#c47
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-2011-1065.html