Remove issue with Vanilla install of Fedora 7
Christopher T Vogan
cvogan at us.ibm.com
Thu Mar 20 17:53:28 EDT 2008
That looks like the issue I am seeing.
I have a question regarding this. I have system that is running lower
levels of Citi patched kernels i.e.(2.6.21) and It does not have this
problem.
But I have a redhat el5 system with a 2.6.18-53.1.6.el5 and it has the same
issue I reported below.
How come the Citi Patched systems do not have this problem? It might have
been cought sooner by us. As We will catch our of order close
rename/remove's from Linux as file names > 8 chars are invalid on IBM
manframes.
Christopher Vogan
Dept. W98 NFS Development & Test
Trond Myklebust
<trond.myklebust@
fys.uio.no> To
Christopher T Vogan/San
03/20/2008 04:23 Jose/IBM at IBMUS
PM cc
nfsv4 at linux-nfs.org
Subject
Re: Remove issue with Vanilla
install of Fedora 7
On Thu, 2008-03-20 at 09:29 -0600, Christopher T Vogan wrote:
> I have been testing vanilla installs of Suse, Redhat and Fedora with
> NFSv4.
> I have stumbled upon a issue that I can not explain.
> The issue is the Linux client (Fedora 7) sends a CLOSE call. Before
> the server replies to the CLOSE the Linux client issue a rename. I
> wanted a remove I know why the linux client did that, it thinks the
> file is still open. What I do not understand is why did the Linux
> client not wait for the CLOSE call to reply before trying to remove
> the file?
> In this case the remove failed because of an invalid file name
> NAMETOOLONG which is expected in this case..
>
> This issue does not happen on a system that has CITI kernel with
> patches and Userland utilities CITI provides. I am wondering if I have
> a configuration issue. I never saw this problem with prior or newer
> kernels. Is this something that the patched kernels resolve?
>
> In the network trace (the part of interest):
>
> CALL CLOSE
> CALL LOOKUP <- rename to replace remove
> REPLY CLOSE
> REPLY LOOKUP
>
>
> The test program does 4 things in this order to recreate this issue.
> OPEN fd
> STAT fd
> CLOSE fd
> REMOVE fd
>
>
> I gathered NFS client and RPC debug info and a network trace. I am
> also including a testcase to reproduce the problem.
> (See attached file: openclose.pcap)(See attached file:
> openclose.txt)(See attached file: openclose.c)
>
> Christopher Vogan
> Dept. W98 NFS Development & Test
That looks very much like the bug described in
http://bugzilla.linux-nfs.org/show_bug.cgi?id=150
The fix was merged into 2.6.24-rc1. You can find it documented at
http://git.linux-nfs.org/?p=trondmy/nfs-2.6.git&a=commitdiff&h=a49c3c7736a2e77931dabc5bc4a83fb4b2da013e
Cheers
Trond
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://linux-nfs.org/pipermail/nfsv4/attachments/20080320/82f8f9d5/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
Url : http://linux-nfs.org/pipermail/nfsv4/attachments/20080320/82f8f9d5/attachment.gif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pic16576.gif
Type: image/gif
Size: 1255 bytes
Desc: not available
Url : http://linux-nfs.org/pipermail/nfsv4/attachments/20080320/82f8f9d5/attachment-0001.gif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ecblank.gif
Type: image/gif
Size: 45 bytes
Desc: not available
Url : http://linux-nfs.org/pipermail/nfsv4/attachments/20080320/82f8f9d5/attachment-0002.gif
More information about the NFSv4
mailing list