mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nathan Scott <nathans@sgi.com>
To: Timothy Miller <miller@techsource.com>
Cc: linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: Re: Increasing number of inodes after format?
Date: Wed, 9 Jun 2004 10:32:52 +1000	[thread overview]
Message-ID: <20040609103252.H1200131@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <40C62F2F.4090801@techsource.com>; from miller@techsource.com on Tue, Jun 08, 2004 at 05:27:11PM -0400

On Tue, Jun 08, 2004 at 05:27:11PM -0400, Timothy Miller wrote:
> I was involved in a discussion a while back where it was explained that 
> ext2/3 allocate a certain maximum number of inodes at format time, and 
> you cannot increase that number later.
> 
> It was also mentioned that one or more of the journaling file systems 
> (XFS, JFS, Reiser, etc.) either dynamically allocated inodes or could 
> increase the maximum later if the pre-allocated set got used up.
> 
> Could someone please repeat for me which filesystems have dynamic 
> maximum inode counts?

XFS does dynamic inode allocation, there is no preallocated set.
Steve also recently implemented dynamic space reclaim for ondisk
inode clusters too, once they're no longer used.  XFS puts a cap
on the amount of space that can be used for inodes at mkfs time
(25% iirc), and this can be adjusted later via "xfs_growfs -m".

I don't know enough about the other filesystems to answer for them
though.

cheers.

-- 
Nathan

  reply	other threads:[~2004-06-09  0:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-08 21:27 Timothy Miller
2004-06-09  0:32 ` Nathan Scott [this message]
2004-06-09  9:42 ` Jan Kara
2004-06-09 10:06   ` Christoph Hellwig
2004-06-09 16:09     ` Hans Reiser
2004-06-09 20:07 ` Dave Kleikamp
2004-08-07 17:53   ` Hans Reiser

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=20040609103252.H1200131@wobbly.melbourne.sgi.com \
    --to=nathans@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@oss.sgi.com \
    --cc=miller@techsource.com \
    /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

all inboxes | Powered by JetHome®