LX0-103 · Question #182
Which of the following Linux filesystems pre-allocates a fixed number of inodes at filesystems make/creation time, and does NOT generate them as needed?
The correct answer is A. ext3. ext3 pre-allocates a fixed inode table at filesystem creation time, unlike JFS, ReiserFS, and XFS which generate inodes dynamically.
Question
Which of the following Linux filesystems pre-allocates a fixed number of inodes at filesystems make/creation time, and does NOT generate them as needed?
Options
- Aext3
- Bjfs
- Creiserfs
- Dxfs
How the community answered
(32 responses)- A91% (29)
- B6% (2)
- D3% (1)
Why each option
ext3 pre-allocates a fixed inode table at filesystem creation time, unlike JFS, ReiserFS, and XFS which generate inodes dynamically.
ext3, like ext2 and ext4, uses mkfs.ext3 to allocate a fixed-size inode table at format time based on a ratio of filesystem size to expected number of files. Once all pre-allocated inodes are consumed, no new files can be created even if free disk space remains.
JFS (IBM Journaled File System) dynamically allocates inodes as files are created rather than reserving them at format time.
ReiserFS uses a dynamic B+ tree structure to store directory entries and metadata, allocating inode-equivalent records on demand.
XFS dynamically allocates inodes in chunks as the filesystem needs them, rather than pre-allocating a fixed table at mkfs time.
Concept tested: Linux filesystem inode pre-allocation vs dynamic allocation
Source: https://www.kernel.org/doc/html/latest/filesystems/ext4/globals.html
Topics
Community Discussion
No community discussion yet for this question.