(I restored the Subject header) Daire Byrne: > > LOOKUP is issued in readdir in NFS, I think. > > Try wireshark and "ls -l /your/nfs/directly". > > When I looked it seems like "ls" triggered just the readdirplus calls > without the lookups. Perhaps you need to check the inodes or mtimes of > the lower branch even if the (same) files are all in the top branch?
No, aufs doesn't behave in such way. Generally the simple "ls" issues readdir(3), while "ls -l" issues stat(2) too. And if your NFS holds the cache, even the readdirplus may not be called. > One last little thing. I can run processes against the aufs branch and > then add branches on the fly without mount complaining but if I try > remove a branch (when running a "find" against the union say) then > mount won't let me remove the branch because it is "in use". Is there > a way to forcibly remove the branch and return an error to the process > that is keeping it open? I would like to be able to pull down the NFS > bottom branch at anytime regardless of what is running (like when > bringing down the network/vpn). I don't think it is a good idea to return an error to userspace, and aufs has no such way to force the error. Why don't you kill your "find" before removing the branch? J. R. Okajima ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
