From: "Shantanu Goel" <Shantanu.Goel@lehman.com>
To: "Lever, Charles" <Charles.Lever@netapp.com>
Cc: "Paul Smith" <pausmith@nortelnetworks.com>, nfs@lists.sourceforge.net
Subject: Re: [NFS PATCH] 2.6.0-test10 Invalidate cached inode attributes after rename
Date: Thu, 04 Dec 2003 10:27:03 -0500 [thread overview]
Message-ID: <3FCF5247.9080901@lehman.com> (raw)
In-Reply-To: <482A3FA0050D21419C269D13989C6113020AC80D@lavender-fe.eng.netapp.com>
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" <Shantanu.Goel@lehman.com> 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
next prev parent reply other threads:[~2003-12-04 15:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 4:25 [NFS PATCH] 2.6.0-test10 Invalidate cached inode attributes after rename Lever, Charles
2003-12-04 15:27 ` Shantanu Goel [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-04 15:34 Lever, Charles
2003-12-04 17:20 ` Paul Smith
2003-11-26 19:41 Shantanu Goel
2003-12-04 0:42 ` Paul Smith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3FCF5247.9080901@lehman.com \
--to=shantanu.goel@lehman.com \
--cc=Charles.Lever@netapp.com \
--cc=nfs@lists.sourceforge.net \
--cc=pausmith@nortelnetworks.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.