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