On Wed, 11 Apr 2007, Krishna Srinivas wrote:
Also regarding write-behind+mtime bug, can you check out the latest code and see if rsync or "cp -a" still sees the problem? Avati made has some changes.
write-behind still has an mtime bug. I "cp -a"'ed a /usr directory and all non-empty files had file creation time/date for their mtime rather than the original mtime. Directories have the correct mtime, and zero-length files have the correct mtime on both underlying filesystems, however, so this is working. But whenever it writes actual data, it seems like it must be doing this after the mtime is set, changing the mtime, or the mtime is never getting set.
Thanks, Brent
