From: bjones@cambria.columbus.oh.us (Bill Jones) Subject: Number of inodes in an extended filesystem Date: 19 Sep 1992 21:44:30 GMT
I just obtained version 8 of the extened file system and noticed that the
number of blocks per inode could be set -- no longer fixed at 4K per inode.
So, I tried to set up my news spool at 2K per inode which I hoped would
clear up the problems I had been having (80MB with 20K inodes and a full
news feed -- I think there were times that linux was running out of inodes
on the disk, not sure though).
Anyway, it turns out that there is a lower limit of 4K per inode in
the code. Is there a kernel based reason behind this or is it just a
decision made on someone's part? I went into the code and fixed it so that
I could have as little as 1K per inode and set up an extended file system
with 1K per inode (~80K inodes).
Yes, the inodes take up a lot of space, about 5MB out of 80MB, and I'm sure
that I will see performance suffer somewhat. But, am I going to run into
unforeseen problems by doing this? So far, I've not had any trouble
(fingers crossed), but what about the future??
Bill