Hi Okajimasan,
I checked your post on 05/23 about your recommendation to move to aufs3.
We are using aufs 2-32. We have plans to move to newer kernel soon. But we
ran into this issue with our current production kernel. Please advice.
Anything else you want me to check/try? Pl let me know.
thank you.
<4>[ 178.727630] Call Trace:
<4>[ 178.727635] [<ffffffff8114a849>] aufs_permission+0x8a/0x2a8
<4>[ 178.727640] [<ffffffff81047fa5>] ? autoremove_wake_function+0x0/0x34
<4>[ 178.727645] [<ffffffff813116f2>] ? __mutex_lock_slowpath+0x26c/0x294
<4>[ 178.727650] [<ffffffff8109687a>] __link_path_walk+0x8b/0xca2
<4>[ 178.727655] [<ffffffff81097627>] path_walk+0x47/0x8a
<4>[ 178.727660] [<ffffffff81098423>] do_filp_open+0x146/0x98b
<4>[ 178.727665] [<ffffffff81312cf8>] ? _spin_unlock+0x13/0x2e
<4>[ 178.727669] [<ffffffff81312cf8>] ? _spin_unlock+0x13/0x2e
<4>[ 178.727674] [<ffffffff810a15dd>] ? alloc_fd+0x111/0x123
<4>[ 178.727678] [<ffffffff8108bb78>] do_sys_open+0x5e/0x111
<4>[ 178.727683] [<ffffffff810c1885>] compat_sys_open+0x15/0x17
<4>[ 178.727687] [<ffffffff810260c5>] cstar_dispatch+0x7/0x2b
bash-4.1# cat /proc/mounts
rootfs / rootfs rw 0 0
none / aufs rw,relatime,si=586e167e29633325,trunc_xino 0 0
none /.overlay tmpfs rw,relatime,size=604508k,nr_inodes=503755,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=604508k,nr_inodes=503755 0 0
tmpfs /.deltas tmpfs rw,relatime,size=32768k,nr_inodes=503755 0 0
tmpfs /var/run tmpfs rw,relatime,size=32768k,nr_inodes=503755 0 0
tmpfs /var/tmp/agents tmpfs rw,relatime,size=32768k,nr_inodes=503755 0 0
tmpfs /var/core tmpfs rw,relatime,size=403004k,nr_inodes=503755 0 0
tmpfs /var/log tmpfs rw,relatime,size=403004k,nr_inodes=503755 0 0
tmpfs /dev tmpfs rw,relatime,size=1024k,nr_inodes=503755 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:[4026531928] proc rw,nosuid,nodev,noexec,relatime 0 0
bash-4.1#
bash-4.1# ls -l /sys/module/aufs/*
total 0
-r--r--r-- 1 root root 4096 May 30 06:35 brs
bash-4.1# ls -l /sys/module/aufs/
total 0
drwxr-xr-x 2 root root 0 May 30 06:35 parameters
bash-4.1# ls -l /sys/module/aufs/parameters/
total 0
-r--r--r-- 1 root root 4096 May 30 06:35 brs
bash-4.1# cat /sys/module/aufs/parameters/brs
1
bash-4.1# ls -l /sys/fs/
aufs/ ext4/
bash-4.1# ls -l /sys/fs/
aufs/ ext4/
bash-4.1# ls -l /sys/fs/aufs
total 0
drwxr-xr-x 2 root root 0 May 30 06:43 si_586e167e29633325
bash-4.1# ls -l /sys/fs/aufs/si_586e167e29633325/
total 0
-r--r--r-- 1 root root 4096 May 30 06:43 br0
-r--r--r-- 1 root root 4096 May 30 06:43 br1
-r--r--r-- 1 root root 4096 May 30 06:43 xi_path
bash-4.1# cat /sys/fs/aufs/si_586e167e29633325/br0
/=rw
bash-4.1# cat /sys/fs/aufs/si_586e167e29633325/br1
/=ro
bash-4.1# cat /sys/fs/aufs/si_586e167e29633325/xi_path
/.aufs.xino
bash-4.1# uname -a
Linux mt232 2.6.32.28 #1 SMP PREEMPT Tue May 29 19:55:40 PDT 2012 x86_64
x86_64 x86_64 GNU/Linux
bash-4.1# dmesg | grep aufs
[ 0.401340] aufs 2-32
[ 32.196969] aufs test_add:248:busybox[704]: uid/gid/perm /squashed-root
0/0/0555, 0/0/0755
bash-4.1#
CONFIG_AUFS_FS=y
CONFIG_AUFS_BRANCH_MAX_127=y
# CONFIG_AUFS_BRANCH_MAX_511 is not set
# CONFIG_AUFS_BRANCH_MAX_1023 is not set
# CONFIG_AUFS_BRANCH_MAX_32767 is not set
# CONFIG_AUFS_HINOTIFY is not set
# CONFIG_AUFS_RDU is not set
# CONFIG_AUFS_SP_IATTR is not set
# CONFIG_AUFS_SHWH is not set
# CONFIG_AUFS_BR_RAMFS is not set
# CONFIG_AUFS_BR_FUSE is not set
CONFIG_AUFS_BDEV_LOOP=y
# CONFIG_AUFS_DEBUG is not set
this is what is in debugfs at normal time.
bash-4.1# ls -l /debug/aufs/
total 0
drwxr-xr-x 2 root root 0 May 30 06:30 si_586e167e29633325
bash-4.1# ls -l /debug/aufs/si_586e167e29633325/
total 0
-r--r--r-- 1 root root 0 May 30 06:30 xi0
-r--r--r-- 1 root root 0 May 30 06:30 xi1
-r--r--r-- 1 root root 0 May 30 06:30 xib
bash-4.1# cat /debug/aufs/si_586e167e29633325/xi0
1, 144x4096 167000
bash-4.1#
bash-4.1# cat /debug/aufs/si_586e167e29633325/xi1
1, 208x4096 129680
bash-4.1# cat /debug/aufs/si_586e167e29633325/xib
8x4096 4096
bash-4.1#
_________________________________________________________________
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: Wednesday, May 30, 2012 12:44 AM
Subject: Re: aufs locking issue?
Hello Prasad,
Prasad Koya:
> Hi=0A=0AWe use aufs2 (rpm installed is aufs2-util. how else do i find out
w=
> hich version of aufs is i'm using) in our system which has 2.6.32.28 64bit
=
When the aufs module is loaded, it prints its version.
Also you can check it via /sys/module/aufs/version.
As you might know, aufs for linux-2.6.32 is not maintained anymore. It
stopped since Aug 2011.
Current aufs2 supports linux-2.6.3[5-9] (and aufs3 supports linux-3.x),
and I made an announcement which says "aufs2 will end in a week or two"
Here is my suggestion.
- upgrade the aufs module to the last version of aufs2.1-32, if your
version is older.
or
- upgrade the linux kernel which aufs supports currently, if you can.
If you give me necessary informations which the aufs README file
describes, I *may* advice more.
J. R. Okajima
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
