Okajima,
   Thanks for looking into this.
   If there is a chance of this warning coming even after using udba=notify, I
   am not inclined to mounting with that option and taking the performance hit.
   Meanwhile I'll try to see if I can print (in the warning) full path of file
   or directory UDBA that is causing is. This way I can make the userspace
   touch that file or dir through the aufs mount and not underlying branch
   directly.
   Prasad

   On Sun, Feb 10, 2013 at 9:37 PM, <[1]sf...@users.sourceforge.net> wrote:

     Hello Prasad,
     Prasad Koya:

   > Looking at aufs3.x sources, I see the same behavior ie., that if code ever
   > hits below condition it evaluates to true (if CRAMFS is not configured). I
   > can try enabling CONFIG_AUFS_HNOTIFY option but is there is anyway I could
   > verify that enabling this config and using mount option "fixes" this
   issue.

     Sorry for my slow response.
     If I remember correctly, even if you set udba=notify, there are a few
     cases left the warning produced.
     (from the aufs manual)
     ----------------------------------------
     To rename/rmdir a directory on a branch directory may reveal the same
     named
     directory on the lower branch. Aufs tries re-lookuping the renamed
     directory and the revealed directory and assigning different inode
     number to them. But the inode number including their children can be a
     problem. The inode numbers will be changed silently, and
     aufs may produce a warning. If you rename a directory repeatedly and
     reveal/hide the lower directory, then aufs may confuse their inode
     numbers too. It depends upon the system cache.
     When you make a directory in aufs and mount other filesystem on it,
     the directory in aufs cannot be removed expectedly because it is a
     mount point. But the same named directory on the writable branch can
     be removed, if someone wants. It is just an empty directory, instead
     of a mount point.
     Aufs cannot stop such direct rmdir, but produces a warning about it.
     ----------------------------------------
     I will develop a script to reproduce the warning, bu I am not sure when
     it succeeds.
     J. R. Okajima

References

   1. mailto:sf...@users.sourceforge.net
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013 
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb

Reply via email to