On Sun 21 August 2011 11:13:53 Mick did opine thusly: > On Sunday 21 Aug 2011 05:47:16 Hilco Wijbenga wrote: > > On 20 August 2011 21:21, Nilesh Govindarajan <cont...@nileshgr.com> wrote: > > > On 08/21/2011 09:00 AM, Hilco Wijbenga wrote: > > >> Yes, df -i says /portage is out of inodes. I've never run > > >> into that before. I reran mke2fs to increase the inode > > >> count and that fixed things. > > > > > > Sorry for the drop in, but I never knew that mke2fs can > > > increase the number of inodes! > > > I think I'll now place the portage tree on an ext2 disk > > > image to speed up things, / has got fragmented badly due to > > > portage tree :-\> > > Well, for the record, I'm not using ext2 but ext3 (mke2fs -j). > > Although, now that I think about it, I suppose there's not much > > point in having the Portage tree on a journaled FS. > > > > If you run man mke2fs, you should check out -N and -i. It was > > trial-and-error (for me, anyway) to find the right number. > > Presumably, -I fits in there somewhere as well. Do note that it > > only works when creating the FS, you can't change the inode > > count dynamically. > I've never run out of inodes, even on small partitions. I just let > ext4 make a fs with its default settings. Is there a magic formula > to determine how many inodes are optimal?
No, there's no such formula. The answer to "How many inodes do I need?" is always "How many do you need?" -- alan dot mckinnon at gmail dot com
