Hi Trond et al,
The following one line patch invalidates the attributes of the
underlying inode when a file is renamed. Some filesystems update ctime
upon rename(). One such filesystem is ext3, and a comment in the
relevant code there indicates this is true with other Unix filesystems
as well.
The following problem was observed on Fedora Core 1 running a stock
kernel.org 2.6.0-test10.
The server is running Solaris 2.8 but I have verified the same issue
exists with a server running Linix 2.4.22. These operations a done via
a Perl script.
1. Check out a CVS repository into an NFS mounted directory.
2. Move files from CVS working directory into another directory in the
same filesystem.
3. Tar up the resultant directory.
4. Tar prints lots of "file changed after we read it" messages.
Tar obtains ctime via stat() before reading the file and compares it to
the ctime obtained via fstat() after having read the file. The two
differ because the intervening open() forces an attribute refresh due to
CTO consistency at which time ctime is updated. Forcing a cache
invalidation during rename() eliminates this particular scenario.
Thanks,
Shantanu
--- 2.6.0-test10/fs/nfs/dir.c.~1~ 2003-10-17 17:43:11.000000000 -0400
+++ 2.6.0-test10/fs/nfs/dir.c 2003-11-26 12:42:27.000000000 -0500
@@ -1257,6 +1257,7 @@
nfs_zap_caches(new_dir);
nfs_zap_caches(old_dir);
+ NFS_CACHEINV(old_inode);
error = NFS_PROTO(old_dir)->rename(old_dir, &old_dentry->d_name,
new_dir, &new_dentry->d_name);
out:
------------------------------------------------------------------------------
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
%% "Shantanu Goel" <[email protected]> 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?
--
-------------------------------------------------------------------------------
Paul D. Smith <[email protected]> HASMAT--HA Software Mthds & Tools
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
These are my opinions---Nortel Networks takes no responsibility for them.
-------------------------------------------------------
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs