From: "Shantanu Goel" Subject: Re: [NFS PATCH] 2.6.0-test10 Invalidate cached inode attributes after rename Date: Thu, 04 Dec 2003 10:27:03 -0500 Sender: nfs-admin@lists.sourceforge.net Message-ID: <3FCF5247.9080901@lehman.com> References: <482A3FA0050D21419C269D13989C6113020AC80D@lavender-fe.eng.netapp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Cc: "Paul Smith" , nfs@lists.sourceforge.net Return-path: Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.11] helo=sc8-sf-mx1.sourceforge.net) by sc8-sf-list2.sourceforge.net with esmtp (Exim 4.24) id 1ARvO0-0007OD-D1 for nfs@lists.sourceforge.net; Thu, 04 Dec 2003 07:27:24 -0800 Received: from mail-haw.bigfish.com ([12.129.199.61] helo=mail22-haw-R.bigfish.com) by sc8-sf-mx1.sourceforge.net with esmtp (TLSv1:AES256-SHA:256) (Exim 4.24) id 1ARvO0-00077e-1r for nfs@lists.sourceforge.net; Thu, 04 Dec 2003 07:27:24 -0800 To: "Lever, Charles" In-Reply-To: <482A3FA0050D21419C269D13989C6113020AC80D@lavender-fe.eng.netapp.com> Errors-To: nfs-admin@lists.sourceforge.net List-Unsubscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Post: List-Help: List-Subscribe: , List-Archive: Stock 2.4 kernels don't exhibit this behaviour because they always invalidate attributes for the last component of the path if CTO is enabled, see fs/nfs/dir.c:nfs_lookup_verify_inode(). In 2.6 and 2.4 kernels such as AS3's 2.4.21, with the newer CTO patches, this code was changed to only do so when the file is being opened. I am surprised you are seeing this on 2.4.20 since I can't replicate it on 2.4.22. Shantanu Lever, Charles wrote: >>%% "Shantanu Goel" writes: >> >> sg> 1. Check out a CVS repository into an NFS mounted directory. >> sg> 2. Move files from CVS working directory into another >>directory in the >> sg> same filesystem. >> sg> 3. Tar up the resultant directory. >> sg> 4. Tar prints lots of "file changed after we read it" messages. >> >>Interesting: I see this exact same message when taring up the contents >>of a ClearCase view (in 2.4.20-x)... even though I'm 100% >>positive that >>no one but me is touching those files. Is this scenario relevant to a >>kernel that old as well? >> >> > >yes, steve dickson at red hat also found this problem in 2.4.21. > > > ------------------------------------------------------------------------------ This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice. ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs