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?
Thanks.
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
> 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?
ReiserFS also does not have any particular limit on the number of inodes
(because it actually does not have any ;).
Honza
--
Jan Kara <[email protected]>
SuSE CR Labs
On Wed, Jun 09, 2004 at 11:42:18AM +0200, Jan Kara wrote:
> ReiserFS also does not have any particular limit on the number of inodes
> (because it actually does not have any ;).
they're just called stat_data in reiserfs.
Christoph Hellwig wrote:
>On Wed, Jun 09, 2004 at 11:42:18AM +0200, Jan Kara wrote:
>
>
>> ReiserFS also does not have any particular limit on the number of inodes
>>(because it actually does not have any ;).
>>
>>
>
>they're just called stat_data in reiserfs.
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to [email protected]
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
>
>
and there is no limit on them, but there is an objectid limit which is
32 bits in V3 and 64 bits in V4.
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.
--
David Kleikamp
IBM Linux Technology Center