On Wed, Dec 23, 2009 at 2:51 PM, <[email protected]> wrote: > The root dir is special (currently), and the .wh..wh..opq just under the > root dir (mount-point) has no meaning. > Try, > # mkdir -p /tmp/dir1/d /tmp/dir2/d /tmp/aufs > # touch /tmp/dir1/d/file1 /tmp/dir2/d/file2 /tmp/dir1/d/.wh..wh..opq > # mount -t aufs -o br=/tmp/dir1:/tmp/dir2 aufs /tmp/aufs
Okay bad example! Your eample works fine when I use the local /tmp drive. In that case it must have something to do with the lower branch being NFS. If I do something like the following then it ignores the ".wh..wh..opq" file in the upper branch (even when not in the root dir). # mkdir -p /tmp/dir1 /tmp/dir2 /tmp/aufs # mount server:/test /tmp/dir2 # mkdir -p /tmp/dir1/d /tmp/dir2/d # touch /tmp/dir1/d/file1 /tmp/dir2/d/file2 /tmp/dir1/d/.wh..wh..opq # mount -t aufs -o br=/tmp/dir1:/tmp/dir2 aufs /tmp/aufs # ls -hl /tmp/aufs/d/ total 0 -rw-rw-rw- 1 root root 0 2009-12-23 15:40 file1 -rw-rw-rw- 1 root root 0 2009-12-23 15:42 file2 The ".wh..wh.opq" file is definitely in dir1/d/ yet still I see file2 which is only in dir2/d/. The NFS server is normally set to be read-only if that makes any difference. 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
