Continuing the discussion about the Gentoo distro filesystem in a more appropriate forum:
caker [originally in Sales Questions and Answers::Sounds cool, have questions] wrote:
pclissold wrote:
I think the extra size is due to the number of files needed during the build and the current 4k block size on the filesystem.
With the last Gentoo template update, I switch to 1k block size:
Code:
[root@host4 root]# tune2fs -l /vbin/fs/gentoo-1.4-small-1.2 | grep "Block size"
Block size: 1024
But even still, the "max number of files" limit was hit. Perhaps I missed something...
-Chris
I just installed the Gentoo distro on the minimum size partition and while there is >500MB of free space, there are only 189 inodes free.
Code:
fremont gentoo-test # tune2fs -l /dev/ubd/3 | grep "[Bb]lock\|[Ii]node"
Inode count: 135168
Block count: 1076224
Reserved block count: 0
Free blocks: 575531
Free inodes: 189
First block: 1
Block size: 1024
Blocks per group: 8192
Inodes per group: 1024
Inode blocks per group: 128
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Journal inode: 8
fremont gentoo-test #
The filesystem seems to have been created with a bytes-per-inode ratio of 8k but the system contains ~135 000 files with an average size of around 3k.
Could this be the reason for running out of files when creating the distro and having to make the partition larger than necessary? It also need looking at because installing the distro on the minimum size partition gives you a system that is all but unusable. Since you can't increase the number of inodes on an existing filesystem, the only options at the moment are to expand the partition (but you'll still likely end up short of inodes) or move the whole thing onto a new partition with a smaller bytes-per-inode ratio.
FAQ
Search
Members
Register
Login [ Anonymous ]
