[Lustre-devel] statahead feature

Andreas Dilger adilger at sun.com
Mon Jul 28 15:02:58 PDT 2008

On Jul 24, 2008  22:04 -0700, Ragnar Kj�rstad wrote:
> On Thu, Jul 24, 2008 at 9:41 PM, Alex Zhuravlev <Alex.Zhuravlev at sun.com> wrote:
> > no, I don't think we need lock always: you just did getattr and fill inode
> > with fresh attributes, then you release lock, somebody changes attributes
> > on the server and only then userspace application gets attributes (already
> > non-fresh). so, what lock gives you in this case?
> If I have an application that does:
> 1. Update stat data on one node.
> 2. Barrier
> 3. Read the same stat data on a different node
> I should be guaranteed to get the correct data, right?
> So stat should return data that was valid either when the system call
> started, when it ended, or somewhere in between. (not data that was
> invalid even before the systemcall started)

That depends on what stat data was changed.  If it was e.g. atime then
there is no guarantee that the other node will get an updated copy.
If there is a file write that updates mtime then there is no guarantee
that other clients will get an updated mtime if they already have a file

Cheers, Andreas
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.

More information about the lustre-devel mailing list