From: Chris Adams (cmadams@hiwaay.net)
Date: Wed Mar 24 2004 - 22:11:31 EST
I am seeing inconsistencies in the cluster file system in the file
access time stamp. Under some conditions (which I haven't figured out
yet), one cluster member will see a different atime than the other. The
mtime and ctime are the same on both, and the member that last wrote to
the file sees the correct atime, but the other member (which is the CFS
server for the domain) sees the atime as the same as the mtime.
This is quite annoying, as it is happening on mailbox files (which if
atime >= mtime, the mailbox is considered "read"). The fileset in
question is NOT mounted "noatimes".
Any suggestions? Is this expected behaviour?
-- Chris Adams <cmadams@hiwaay.net> Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble.
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:55 EDT