On Mon, Dec 21, 2009 at 5:08 PM, Daire Byrne <[email protected]> wrote: > On Fri, Dec 18, 2009 at 12:07 AM, <[email protected]> wrote: >> If you access a dir in aufs, aufs accesses every branch. >> If it is a non-dir, aufs searches the first one only. >> You may want the 'dirperm1' aufs option for the dir. But it is dropped >> in aufs2. > > Yes that could explain that one. > >> If you really stop aufs accessing your lower NFS branch, then you should >> create a file named ".wh..wh.opq" in all directories on the upper >> branch. It tells aufs that the dir is "opaque" and aufs will not search >> the lower dir. > > Oops - I completely missed this functionality. I can probably write > some logic to create these files where I need them - thanks. It isn't > as flexible as just letting aufs union every dir but at least it does > get rid of all the slow NFS calls.
Actually even with the ".wh..wh..opq" files in every dir of a tree, there are still a lot of NFS calls happening. There are still the readdir calls and lots of access calls on the dirs to get the perms. I suppose I still need the dirperm1 option to completely eradicate these. I thought the opaque files would essentially disable the union for that dir but actually if I create a new file in the lower (NFS) branch I can see it in the aufs union even though there is a ".wh..wh..opq" in the top branch for that dir. Probably the opaque stuff isn't working at all for me? (aufs-2-standalone.tree-31-20091012). Is it ".wh..wh..opq" files or "wh..wh.opq" that I should be creating (I made both anyway). Thanks again for your insight, Daire ------------------------------------------------------------------------------ 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
