Dear Junjiro, Am Montag, 16. November 2009 14:19:57 schrieb [email protected]: > > [r...@gibraltar-500 ~]# df -i /system/ramdisks/var/ > > =46ilesystem Inodes IUsed IFree IUse% Mounted on > > tmpfs 31698 592 31106 2% /system/ramdisks/var > > [r...@gibraltar-500 ~]# df -i /system/root/ > > =46ilesystem Inodes IUsed IFree IUse% Mounted on > > /dev/loop0 38250 38250 0 100% /system/root > > > > which should result in a maximum size of roughly 150kB. > > No, you are misunderstanding the aufs manual and the size of XINO. > The size depends upon the maximum inode number, instead of the number of > inodes. If you have 10 inodes, you may expect the inode numbers are > assigned such like 100, 101, 102 ... 109. But the filesystem can assign > any number for them such like 99, 9000, 100, 9999, 2222, 10000 .... > If your maximum inode number is 10000 even if you have only 10 inodes, > then the size of XINO will look about 10000 x 4 bytes = 40KB (if the > size of your inode is 4bytes).
Ah, thanks for clarifying. > But the size of XINO is not an issue. You should look at how many blocks > it consumes. Generally, a file on a filesystem may not be assigned disk > blocks for the hole in it. It is called sparse file. If you create a new > file, write a byte at the top of it, seek to 1MB , and write another > byte, then the filesize will look as 1MB+1. But the allocated disk > blocks are only two. If the block size of your filesystem is 4k, then > the file which looks 1MB+1 as its size, consumes only 8kb actually. Understood. However, I don't think this to be the case when the xino is stored on a tmpfs branch - in practice, I see the memory being used, so it seems unlikely that it is a sparse file in this case (or maybe it just doesn't have enough holes in it to be noticable). > > don't yet have a feeling which one they might be. Is noxino in common > > use=20 among other users of aufs(2)? If not, how do others cope with this > > huge=20 "waste" of RAM, especially on embedded systems for which aufs2 is > > otherwise= a=20 > > huge advantage? > > While I don't know how many people uses noxino actually, the xino= > option is set by default and I guess many people are using it. For the record, I have now switched to using noxino to avoid the memory usage (which breaks services on our embedded systems with only 256MB RAM), and so far everything seems to work. We have tested squid, havp, and amavis so far and have not yet encountered any issues. I will report back if anything unexpected happens. PS: With recent discussions on LKML, what are the chances of aufs2 being merged upstream? best regards, Rene -- ------------------------------------------------- Gibraltar firewall http://www.gibraltar.at/
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july
