Operating Systems - Inode Structure - File Metadata & Block Pointers
If a file system uses triple indirect pointers in its inode structure, what is a potential downside when accessing a small file that fits entirely within direct blocks?
If a file system uses triple indirect pointers in its inode structure, what is a potential downside when accessing a small file that fits entirely within direct blocks?
hard🎤 Interviewer Follow-up Q15 of Q15
Step-by-Step Solution
Step 1: Understand inode fixed size
Inodes have a fixed size that includes space for direct and indirect pointers, regardless of file size.Step 2: Analyze impact on small files
Including triple indirect pointers increases inode size, which can waste space when storing many small files.Step 3: Clarify access speed for small files
Accessing small files uses direct pointers only; indirect pointers are not traversed, so no speed penalty.Step 4: Confirm allocation behavior
Indirect blocks are allocated only when needed; small files do not allocate them.Final Answer:
Option A -> Option AQuick Check:
Fixed inode size with many pointers wastes space for small files [OK]
Quick Trick: Fixed inode size -> wasted space for small files with many pointers
Common Mistakes:
MISTAKES- Assuming indirect pointers slow down small file access
- Believing indirect blocks are allocated for small files
- Thinking triple indirect pointers have no impact on inode size
Trap Explanation:
PITFALL- Option B is tempting but indirect pointers are not traversed for small files. Option C is false because indirect blocks are allocated on demand. Option D ignores inode size implications.
Interviewer Note:
CONTEXT- Probes deep understanding of inode design trade-offs and file size impact.
Master "Inode Structure - File Metadata & Block Pointers" in Operating Systems
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Operating Systems Quizzes