From: Anthony Metcalf <Anthony.Metcalf@anferny.ath.cx>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] how does Gentoo's mke2fs determine how many inodes to create?
Date: Fri, 11 Jul 2008 13:35:02 +0100 [thread overview]
Message-ID: <48775376.3010709@anferny.ath.cx> (raw)
In-Reply-To: <20080711151500.3ae97b4f@ilievnet.com>
Daniel Iliev wrote:
> On Fri, 11 Jul 2008 13:16:53 +0200
> Miernik <public@public.miernik.name> wrote:
>
>
> /etc/mke2fs.conf - this file contains the default options plus several
> presets.
>
> The number of inodes can be specified at creation time with the "-N"
> parameter. AFAIK it cannot be changed afterwards.
>
>
>
You can though, dd the partition to another drive, re-format, and dd it
back....
Anthony
--
gentoo-user@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-07-11 12:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 11:16 [gentoo-user] how does Gentoo's mke2fs determine how many inodes to create? Miernik
2008-07-11 12:15 ` Daniel Iliev
2008-07-11 12:35 ` Anthony Metcalf [this message]
2008-07-11 12:39 ` Dirk Heinrichs
2008-07-11 13:03 ` Daniel Iliev
2008-07-11 13:10 ` Dirk Heinrichs
2008-07-11 13:34 ` Anthony Metcalf
2008-07-11 15:45 ` Alan McKinnon
2008-07-11 17:51 ` Robert Bridge
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=48775376.3010709@anferny.ath.cx \
--to=anthony.metcalf@anferny.ath.cx \
--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