- /proc/mounts (instead of the output of mount(8))
# cat /proc/mounts
rootfs / rootfs rw 0 0
none /mnt/root_base/sys sysfs rw,relatime 0 0
none /mnt/root_base/proc proc rw,relatime 0 0
udev /mnt/root_base/dev tmpfs rw,relatime,size=10240k,mode=755 0 0
10.106.0.21:/vol/boot/netboot/etch64-vserver /mnt/root_base nfs
ro,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,acregmin=300,acregmax=600,acdirmin=300,acdirmax=600,hard,nolock,proto=tcp,port=65535,timeo=7,retrans=3,sec=sys,mountport=65535,addr=10.106.0.21
0 0
10.106.0.21:/vol/boot/netboot/etch64-vserver /mnt/root_base/dev/.static/dev
nfs
ro,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,acregmin=300,acregmax=600,acdirmin=300,acdirmax=600,hard,nolock,proto=tcp,port=65535,timeo=7,retrans=3,sec=sys,mountport=65535,addr=10.106.0.21
0 0 /dev/sda1 /mnt/local ext3
rw,relatime,errors=continue,data=writeback 0 0 none / aufs
rw,relatime,si=586e167b0a1abf25 0 0 tmpfs /lib/init/rw tmpfs
rw,nosuid,relatime,mode=755 0 0 proc /proc proc
rw,nosuid,nodev,noexec,relatime 0 0 sysfs /sys sysfs
rw,nosuid,nodev,noexec,relatime 0 0 none /dev/.static/dev aufs
rw,relatime,si=586e167b0a1abf25 0 0 tmpfs /dev tmpfs
rw,relatime,size=10240k,mode=755 0 0 tmpfs /dev/shm tmpfs
rw,nosuid,nodev,relatime 0 0 devpts /dev/pts devpts
rw,nosuid,noexec,relatime,gid=5,mode=620 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0
- /sys/module/aufs/*
# cat /sys/module/aufs/parameters/brs
1
# cat /sys/module/aufs/parameters/nwkq
4
- /sys/fs/aufs/* (if you have them)
# cat /sys/fs/aufs/si_586e167b0a1abf25/br0
/mnt/local=rw
# cat /sys/fs/aufs/si_586e167b0a1abf25/br1
/mnt/root_base=ro
# cat /sys/fs/aufs/si_586e167b0a1abf25/xi_path
/mnt/local/.aufs.xino
- /debug/aufs/* (if you have them)
no
- linux kernel version
if your kernel is not plain, for example modified by distributor,
the url where i can download its source is necessary too.
2.6.32.2 vanilla
- aufs version which was printed at loading the module or booting the
system, instead of the date you downloaded.
Merged with aufs2-2.6/aufs2-32 (no conflicts):
commit f3f7ad33612eed313b5ae9867ac974f7babcd969
Merge: 036e339... 75fb62d...
Author: J. R. Okajima <hooano...@yahoo.co.jp>
Date: Sat Dec 19 21:09:44 2009 +0900
Merge branch 'aufs2-31' into aufs2-32
- configuration (define/undefine CONFIG_AUFS_xxx)
# grep AUFS .config
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=y
# CONFIG_AUFS_EXPORT 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_BDEV_LOOP=y
# CONFIG_AUFS_DEBUG is not set
- kernel configuration or /proc/config.gz (if you have it)
http://blackprecipice.com/dl/config-2.6.32.2-aufs
- behaviour which you think to be incorrect
leaking file handles (on a idle test system)
- actual operation, reproducible one is better
while (sleep 60);do date && cat /proc/sys/fs/file-nr;done
Tue Dec 29 16:28:14 PST 2009
45376 0 524288
Tue Dec 29 16:29:14 PST 2009
47712 0 524288
Tue Dec 29 16:30:14 PST 2009
50848 0 524288
Tue Dec 29 16:31:14 PST 2009
53152 0 524288
<snip>
118912 0 524288
Tue Dec 29 16:58:14 PST 2009
121440 0 524288
Tue Dec 29 16:59:14 PST 2009
123808 0 524288
Tue Dec 29 17:00:14 PST 2009
127040 0 524288
<snip>
Tue Dec 29 17:55:00 PST 2009
265888 0 524288
Tue Dec 29 17:56:00 PST 2009
268576 0 524288
Tue Dec 29 17:57:00 PST 2009
271104 0 524288
Tue Dec 29 17:58:00 PST 2009
273472 0 524288
Tue Dec 29 17:59:00 PST 2009
276000 0 524288
Tue Dec 29 18:00:00 PST 2009
278336 0 524288
It keeps on growing and growing will exceed the maximum number of file
handles and continue to grow and grow. I left it running overnight and
it reached over 1 million but today I rebooted it with this kernel to
see if I could reproduce with vanilla+aufs only. If there is
any other information I can provide let me know.
Thanks in advance.
--
Kyle Bader - Dreamhost
------------------------------------------------------------------------------
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
