Description of problem: NFSv4 issue with RHEL5 system. Problem also is seen on Fedora 7 and 8 systems. NFSv4 client does not wait for the Close call to return before issuing a remove request. The result is the file is renamed to .nfsxxxxxx before being removed. In a simple test program the close function was issued before the remove. In a network trace you can see the close call, but the nfsv4 client sent a rename before the close call had a chance to return. Version-Release number of selected component (if applicable): Kernel level: 2.6.18-53.1.14.el5 How reproducible: Simple C program: Open fd Stat fd Close fd Remove fd Steps to Reproduce: 1.Mount NFSv4 share 2.Run test program to open,stat,close,remove file to mount point. 3.Unmount NFSv4 share Actual results: The file was not removed. It was renamed then removed after the test program completed. Network trace showed these results. > CALL CLOSE > CALL LOOKUP <- rename to replace remove > REPLY CLOSE > REPLY LOOKUP Expected results: > CALL CLOSE > REPLY CLOSE > CALL REMOVE > REPLY REMOVE Additional info: There is a fix for this problem by University of Michigan CITI NFSv4 team. See Bugzilla: http://bugzilla.linux-nfs.org/show_bug.cgi?id=150 and/OR http://git.linux-nfs.org/?p=trondmy/nfs-2.6.git&a=commitdiff&h=a49c3c7736a2e77931dabc5bc4a83fb4b2da013e
This request was evaluated by Red Hat Product Management for inclusion, but this component is not scheduled to be updated in the current Red Hat Enterprise Linux release. If you would like this request to be reviewed for the next minor release, ask your support representative to set the next rhel-x.y flag to "?".
*** Bug 456445 has been marked as a duplicate of this bug. ***
Unfortunately the previous automated notification about the non-inclusion of this request in Red Hat Enterprise Linux 5.3 used the wrong text template. It should have read: this request has been reviewed by Product Management and is not planned for inclusion in the current minor release of Red Hat Enterprise Linux. If you would like this request to be reviewed for the next minor release, ask your support representative to set the next rhel-x.y flag to "?" or raise an exception.
Fedora has resolved this issue with Patchs from git in Fedroa 8. Can this same patch be used to address the close remove issue reported in this BUG? We are gated from using Redhat kernels because of this issue. Patches below: http://git.linux-nfs.org/?p=trondmy/nfs-2.6.git&a=commitdiff&h=a49c3c7736a2e77931dabc5bc4a83fb4b2da013e
*** This bug has been marked as a duplicate of bug 565974 ***