Okajimasan,
   Thanks for your response. Here is what we have. vanilla aufs2.2-38 patch. We
   didn't touch this patch or anyfiles that this patch touched. This aufs patch
   didn't have CONFIG_AUFS_INOTIFY. I read in one of your posts to enable this
   config option to debug this issue.
   Obtained from git://git.c3sl.ufpr.br/aufs/aufs2-standalone.git.
   Used branch remotes/origin/aufs2.2-38.
   Patches include kbuild, base, proc_map and misc.
   aufs2.2 kbuild patch for linux-2.6.38
   diff --git a/fs/Kconfig b/fs/Kconfig
   index 3db9caa..c9e1f11 100644
   --- a/fs/Kconfig
   +++ b/fs/Kconfig
   @@ -190,6 +190,7 @@ source "fs/romfs/Kconfig"
    source "fs/sysv/Kconfig"
    source "fs/ufs/Kconfig"
    source "fs/exofs/Kconfig"
   +source "fs/aufs/Kconfig"
   :
   :
   I tried this today without much luck:
   mount -t aufs -o dirs=/var/core:/var/log none /tmp/storage
   mkdir /tmp/storage/tdir
   touch /tmp/storage/tdir/d1
   for ((i=0;i<500000;i++)); do rm -rf /var/core/tdir;mkdir /var/core/tdir;done
   here is my mounts again:
   -bash-4.1# cat /proc/mounts
   rootfs / rootfs rw 0 0
   none / aufs rw,relatime,si=92ba869325e3197c 0 0
   none /.overlay tmpfs rw,relatime,size=301980k,mode=755 0 0
   none /proc proc rw,nosuid,nodev,noexec,relatime 0 0
   none /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
   tmpfs /tmp tmpfs rw,relatime,size=301980k 0 0
   tmpfs /.deltas tmpfs rw,relatime,size=65536k 0 0
   tmpfs /var/run tmpfs rw,relatime,size=65536k 0 0
   tmpfs /var/tmp tmpfs rw,relatime,size=65536k 0 0
   tmpfs /var/core tmpfs rw,relatime,size=201320k 0 0
   tmpfs /var/log tmpfs rw,relatime,size=201320k 0 0
   tmpfs /dev tmpfs rw,relatime,size=4096k 0 0
   devpts /dev/pts devpts rw,relatime,mode=600 0 0
   /dev/sda1 /mnt/flash vfat
   rw,dirsync,noatime,gid=88,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp
   437,iocharset=ascii,shortname=mixed,flush,errors=remount-ro 0 0
   /dev/sdb1 /mnt/usb1 vfat
   rw,dirsync,noatime,gid=88,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp
   437,iocharset=ascii,shortname=mixed,flush,errors=remount-ro 0 0
   none net:[4026531976] proc rw,nosuid,nodev,noexec,relatime 0 0
   none /tmp/storage aufs rw,relatime,si=92ba86934db0097c 0 0
   -bash-4.1#
   Will try what you suggested.
   thanks
   Prasad
     _________________________________________________________________

   From: "sf...@users.sourceforge.net" <sf...@users.sourceforge.net>
   To: Prasad Koya <kdp...@yahoo.com>
   Cc: "aufs-users@lists.sourceforge.net" <aufs-users@lists.sourceforge.net>
   Sent: Tuesday, October 16, 2012 7:04 PM
   Subject: Re: aufs Warning: Un-notified UDBA
   Hello Prasad,
   Prasad Koya:
   > aufs au_new_inode:412:Aaa[7803]: Warning: Un-notified UDBA or repeatedly
   renamed dir, b0, tmpfs, admin, hi5959, i4117.
   > We are seeing above warning from aufs. Two questions:
   >
   > 1. Is above message benign? Or does it indicate there is some memory leak
   or something of that sort happening?
   >
   >  2.  Pl  see  my  mounts  below.  I tried running a command like "mv
   /.overlay/test /.overlay/test1; mv /.overlay/test1 /.overlay/test" like
   several 10s of thousand times but I didn't see above warning. Any other way
   I can find out what is it from user space or kernel space that is making
   aufs throw this warning?
   The message doesn't indicate a memory leak. It tells you that
   - you have accessed a file in aufs, and the system stores its inode in
   cache.
   - you made some changes to the file outside of aufs (bypassing aufs).
   - you access the file again in aufs.
   - aufs finds something unmatched between the cached aufs-inode and the
     inode on the branch fs (directly changed inode), and produces the
     warning.
   To reproduce the warning, I'd suggest you the following steps. But I am
   not sure it can surely reproduce since it highly depends upon the cache
   situation.
   - /u = /rw + /ro
   - run "> /u/file" once
   - repeat "stat /u/file > /dev/null" in background
   - repeat "> /rw/file2; mv /rw/file2 /rw/file"
   If you want aufs to support such situation without the warning, then you
   should use the aufs "udba=notify" mount option. It detects the direct
   changes on the branch and aufs simply make the cached inode obsolete.
   If you didn't make any direct changes, then there may be something wrong
   in aufs. Please let me know more details.
   J. R. Okajima
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct

Reply via email to