Operating Systems - Inode Structure - File Metadata & Block Pointers
When a file grows beyond the capacity of direct block pointers in its inode, what sequence of steps occurs to locate the additional data blocks?
When a file grows beyond the capacity of direct block pointers in its inode, what sequence of steps occurs to locate the additional data blocks?
easy🧠🧾 Concept Trace Q12 of Q15
Step-by-Step Solution
Step 1: Recall inode pointer hierarchy
Inodes have a fixed number of direct pointers, followed by single, double, and triple indirect pointers for larger files.Step 2: Understand pointer escalation
When direct pointers are full, the file system uses single indirect pointers, which point to blocks containing more direct pointers.Step 3: Eliminate incorrect escalations
The inode does not skip levels; it uses single indirect before double indirect pointers.Step 4: Clarify inode content storage
Inodes never store file content directly; they only store metadata and pointers.Final Answer:
Option A -> Option AQuick Check:
Single indirect pointers extend data block addressing after direct pointers [OK]
Quick Trick: Direct -> Single Indirect -> Double Indirect pointer escalation
Common Mistakes:
MISTAKES- Skipping pointer levels (double indirect before single indirect)
- Assuming inode can dynamically add direct pointers
- Thinking inode stores file content directly
Trap Explanation:
PITFALL- Option A is tempting for candidates who think pointer levels can be skipped. Option C wrongly assumes inode size is dynamic. Option D confuses inode metadata with data storage.
Interviewer Note:
CONTEXT- Evaluates understanding of inode pointer structure and file block addressing escalation.
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