From: Hans Reiser <reiser@namesys.com>
To: Dave Kleikamp <shaggy@austin.ibm.com>
Cc: Timothy Miller <miller@techsource.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Increasing number of inodes after format?
Date: Sat, 07 Aug 2004 10:53:25 -0700 [thread overview]
Message-ID: <41151715.5090001@namesys.com> (raw)
In-Reply-To: <1086811650.26565.50.camel@shaggy.austin.ibm.com>
Dave Kleikamp wrote:
>On Tue, 2004-06-08 at 16:27, 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?
>>
>>
>
>JFS dynamically allocates inodes as needed. An inode extent (consisting
>of 32 inodes) will also be freed if all of its inodes are freed.
>
>
reiserfs V3 and V4 have stat data not on disk inodes, and they are
dynamically allocated.
prev parent reply other threads:[~2004-08-07 17:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 21:27 Increasing number of inodes after format? Timothy Miller
2004-06-09 0:32 ` Nathan Scott
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 [this message]
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=41151715.5090001@namesys.com \
--to=reiser@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miller@techsource.com \
--cc=shaggy@austin.ibm.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