[Lustre-devel] Attribute caching and OBD_CONNECT_ATTRFID

Oleg Drokin oleg.drokin at oracle.com
Wed Jun 30 11:27:42 PDT 2010


On Jun 30, 2010, at 2:23 PM, Ken Hornstein wrote:

> Alright, so, I had some time to stare at this code some more ... a few
> questions.
>> Currently, the Linux VFS will flag it as "DCACHE_INVALID" and it needs
>> to be revalidated before use.
> This is DCACHE_LUSTRE_INVALID, right?  I couldn't find DCACHE_INVALID
> anywhere.


>>> Could you point me to the section of the code in the Linux client that
>>> does the inode invalidation upon lock cancellation?  I want to make sure
>>> that I follow it and I'm doing the right thing.
>> The majority of this work was done in bug 20433.
> I see the patch has been re-worked a bit in more recent Lustre.  As I
> read it ... this just gets rid of the dentry for the inode, right?
> That forces a new name lookup the next time the file is accesed by
> name, right?  I guess that's how the lack of CONNECT_ATTRFID hasn't
> been noticed.

Right. The only way to encounter attr_by_fid is to execute something like fstat
on an already opened file descriptor.
Also there used to be NFS implications, I think.

> As a side question ... I know it hasn't really been resolved (from what
> I've read on this thread), but going forward should I assume that
> CONNECT_ATTRFID will not be available?  It sounds like from what you
> are saying that it will eventually not be available.

Actually it should be available going forward, at least I hope so.
This is a pretty important feature to ensure that open-unlinked files
work correctly.


More information about the lustre-devel mailing list