[Lustre-devel] Attribute caching and OBD_CONNECT_ATTRFID
kenh at cmf.nrl.navy.mil
Wed Jun 30 11:23:37 PDT 2010
Alright, so, I had some time to stare at this code some more ... a few
>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
>> 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
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.
More information about the lustre-devel