[gentoo-user] how does Gentoo's mke2fs determine how many inodes to create?

[Miernik <public@public.miernik.name>]

I installed Gentoo using the handbook, and the root partition has
4094951424 bytes (a 4 GB USB pendrive), and "mke2fs -j /dev/sda2" as on
http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=1&chap=4#doc_chap4
created me a partition with only 249984 inodes. That was REALLY SILLY of
him, because:

przehyba ~ # df -i /dev/sda2
Filesystem            Inodes   IUsed   IFree IUse% Mounted on
/dev/sda2             249984  249739     245  100% /
przehyba ~ #

I ran out of inodes! Now it cries that the disk ran out of space when I
try to compile anything. I did already get rid of /usr/share/doc/ as
there are many small files there, and purged /var/tmp/ too, but again
emerge quickly fills all possible inodes, and fails.

Why did he did so little inodes? On another machine, which is Debian and
about 5 GB disk, I have 752192 inodes and even on a 3.2 GB one 376096
inodes, so here why did I get so little by default?

What can I do now, besides starting the installation over again from the
beggining, which would be 2 days of work lost!

Any other places besides /usr/share/doc and /var/tmp/ I can look to
recover a lot of inodes? Can someone fix mke2fs so it doesn't do that to
anyone again in the future?

-- 
Miernik
http://miernik.name/

-- 
gentoo-user@lists.gentoo.org mailing list