LX0-103 · Question #58
Which of the following Linux filesystems preallocates a fixed number of inodes at the filesystem's make/ creation time and does NOT generate them as needed? (Choose TWO correct answers.)
The correct answer is A. ext3 C. ext2. ext2 and ext3 both allocate a fixed pool of inodes when the filesystem is created with mkfs, whereas XFS and JFS dynamically generate inodes as files are created.
Question
Which of the following Linux filesystems preallocates a fixed number of inodes at the filesystem's make/ creation time and does NOT generate them as needed? (Choose TWO correct answers.)
Options
- Aext3
- BJFS
- Cext2
- DXFS
- Eprocfs
How the community answered
(19 responses)- A84% (16)
- D11% (2)
- E5% (1)
Why each option
ext2 and ext3 both allocate a fixed pool of inodes when the filesystem is created with mkfs, whereas XFS and JFS dynamically generate inodes as files are created.
ext3 is based on the ext2 on-disk format and inherits its inode allocation model, where mkfs.ext3 calculates and reserves a fixed number of inodes at creation time determined by the bytes-per-inode ratio, leaving no mechanism to create additional inodes later.
JFS (Journaled File System) dynamically allocates inodes from inode allocation groups as needed, so it is not constrained by a fixed inode count set at creation.
ext2 pioneered this fixed inode table approach; the total inode count is written into the superblock at mkfs time and cannot be increased without reformatting, which can cause 'no space left on device' errors even when disk space remains if all inodes are consumed.
XFS uses a dynamic inode allocation scheme that creates inodes on demand within allocation groups, avoiding a fixed preallocated limit.
procfs is a virtual pseudo-filesystem that represents kernel and process information in memory and does not have a conventional inode table created at format time.
Concept tested: Fixed vs dynamic inode allocation in Linux filesystems
Source: https://man7.org/linux/man-pages/man8/mke2fs.8.html
Topics
Community Discussion
No community discussion yet for this question.