William Grant: > Ah, I see. How, then, does the UDBA setting work? The inotify feature in linux is a notifirer. For example, when you specify udba=inotify and you change something on the branch directly, then aufs recieves the event and sets the internal flag whose meaning is "the cached data may be obsoleted". When you access the file (or its parent dir) later, aufs checks whether the cache is still valid or not. If it is obsoleted, aufs discards it and gets new one.
In your case, you wrote to a file on nfs server. But the filesystem aufs is monitoring is the one on nfs client. So udba=inotify is meaningless for you. Generally, aufs trusts the revalidate routine which is implemented in remote filesystem natively. In your case, when you invoke "ls", the revalidate function in NFS confirms the attribute is still valid, and refreshes it if necessary. Aufs calls the revalidate routine for every branchees and gets the latest info. > It is. I can do it dozens of times and it will still be incorrect. Thank you for your tests. I will try ubuntu jaunty kernel with the latest aufs1. I am afraid it may take some days. Currently I am unsure what is wrong at all. J. R. Okajima ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H
