On Mon, Jan 30, 2006 at 12:13:25PM -0800, Vladimir V. Kolpakov wrote: > Hi, > > Most of interest I see around unionfs is about writable union, > while my goal is opposite: totally read-only union, > somewhat we could get with: > > mount -t unionfs -o ro,dirs=/branch1=ro,/branch2=ro none /union > > After failed attempt to get such union working properly,
What do you mean by _properly_? > Is this known bug, or just something out of unionfs specification? The problem is the existance of the dentry cache. I caches some of the information. Since the cache is consulted _before_ unionfs code gets executed, it is possible that the VFS can think that it can get all the information it needs from the cache only. There is really no sane way around it (at least for now). So, you have two options: 1) Don't touch the lower filesystems (prefered) 2) Run uniondbg -g (a hack) Jeff. _______________________________________________ unionfs mailing list [email protected] http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs
