Rene Mayrhofer: > =46irst of all, sorry for not being more specific in my initial email, I wi= > ll try=20 > to give all the the required information now.
Ok, now I can understand your situation. > > - linux kernel version > > 2.6.30.8 As you might know, aufs1 doesn't support linux-2.6.28 and later. So I guess debian people modified the aufs1 source files. > > For > > instance aufs XINO files are such files, and the size of these files are > > listed in /sys/fs/aufs/si_*/xino. They may be the one you are looking > > for. (but I am not sure) > > Possibly. However, I am unable to interpret these: > > [r...@gibraltar-500 ~]# cat /sys/fs/aufs/si_7*/xino > 8x4096 4096 > 0: 1, 696x4096 3320260 > 1: 1, 48x4096 43540 > 8x4096 4096 > 0: 1, 6544x4096 3358868 > 1: 1, 56x4096 152592 According to your /proc/mounts, you have two aufs mounts, /etc and /var. /sys/fs/aufs/si_76a81819/xino shows the information about XINO files for /etc, and si_772cd879/xino is for /var. For /var, there are one XIB(inode bitmap) and two XINO files. Your /sys/fs/aufs/si_772cd879/xino shows that, - XIB consumes 8 blocks in /system/ramdisks/var, - one of XINO files consumes 6544 blocks, - and the other consumes 56 blocks. Since the block size of /system/ramdisks/var is 4k, all of your XINO files for /var consumes (8+6544+56) x 4k = about 2.7MB. I hope this is the answer of your question. See the aufs manual for detail. (from the aufs1 manaul) ---------------------------------------------------------------------- The xino files are always hidden, i.e. removed. So you cannot do `ls \-l xino_file'. If you enable CONFIG_SYSFS, you can check these information through <sysfs>/fs/aufs/<si_id>/xino (for linux\-2.6.24 and earlier, you need to enable CONFIG_AUFS_SYSAUFS too). The first line in <sysfs>/fs/aufs/<si_id>/xino (and xigen) shows the information of the bitmap file, in the format of, .nf <blocks>x<block size> <file size> .fi Note that a filesystem usually has a feature called pre-allocation, which means a number of blocks are allocated automatically, and then deallocated silently when the filesystem thinks they are unnecessary. You do not have to be surprised the sudden changes of the number of blocks, when your filesystem which xino files are placed supports the pre-allocation feature. The rests are hidden xino file information in the format of, .nf <branch index>: <file count>, <blocks>x<block size> <file size> .fi If the file count is larger than 1, it means some of your branches are on the same filesystem and the xino file is shared by them. Note that the file size may not be equal to the actual consuming blocks since xino file is a sparse file, i.e. a hole in a file which does not consume any disk blocks. ---------------------------------------------------------------------- J. R. Okajima ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf
