From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [Gentoo install] Disk full at 35%?
Date: Sun, 21 Aug 2011 11:13:53 +0100 [thread overview]
Message-ID: <201108211114.04507.michaelkintzios@gmail.com> (raw)
In-Reply-To: <CAE1pOi3_GEUuxHvyqan=CxZVEcoUKWd3o2kr=dM+sCpqrtRzxw@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1267 bytes --]
On Sunday 21 Aug 2011 05:47:16 Hilco Wijbenga wrote:
> On 20 August 2011 21:21, Nilesh Govindarajan <contact@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?
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-08-21 10:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-21 1:41 [gentoo-user] [Gentoo install] Disk full at 35%? Hilco Wijbenga
2011-08-21 1:52 ` covici
2011-08-21 3:30 ` Hilco Wijbenga
2011-08-21 4:21 ` Nilesh Govindarajan
2011-08-21 4:47 ` Hilco Wijbenga
2011-08-21 10:13 ` Mick [this message]
2011-08-21 10:30 ` Adam Carter
2011-08-21 10:49 ` Alan McKinnon
2011-08-21 10:46 ` Andrea Conti
2011-08-21 18:14 ` Hilco Wijbenga
2011-08-21 21:24 ` Peter Humphrey
2011-08-21 12:03 ` Alex Schuster
2011-08-21 13:45 ` Andrea Conti
2011-08-21 17:09 ` Alex Schuster
2011-08-21 19:23 ` Andrea Conti
2011-08-21 21:46 ` Alan McKinnon
2011-08-21 3:05 ` Paul Hartman
2011-08-21 3:30 ` Hilco Wijbenga
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201108211114.04507.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox