LPIC-1 Devices, Filesystems and FHS Practice Question
A user reports that they cannot create new files in their home directory even though the filesystem shows free space. Running df -h shows the filesystem at 100 percent inode usage. Which action most directly resolves the immediate problem?
⚠ Common exam trap
The trap here is reading only the percentage in df -h and assuming block exhaustion, when the same command's inode column reveals the real constraint.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Delete unneeded files that consume many inodes, such as old session files or cached mail, to free inode entries.
When df -h reports 100 percent inode usage, the filesystem has no free inode entries even though data blocks may remain. Deleting many small files, such as session or cache files, releases inodes and restores file creation. Expanding the filesystem, remounting with noatime, or adjusting the check interval do not increase available inodes and therefore do not fix the immediate issue.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Run resize2fs to expand the filesystem onto additional space.
Why it's wrong here
resize2fs grows or shrinks a filesystem to fill its underlying block device, but the problem is inode exhaustion, not block exhaustion. Unless the device is enlarged first and the filesystem is recreated or tuned, growing does not automatically add inodes. It also risks data loss if done incorrectly, so it is not the direct fix here.
- ✗
Remount the filesystem with the noatime option to stop inode updates.
Why it's wrong here
noatime prevents access-time updates, reducing write traffic, but it does not create new inode entries or free existing ones. The filesystem has already exhausted its inode table, so mount options cannot restore the ability to allocate new inodes. This is a performance tuning measure, not a remedy for inode exhaustion.
- ✓
Delete unneeded files that consume many inodes, such as old session files or cached mail, to free inode entries.
Why this is correct
A filesystem can run out of inodes while still having free data blocks, and on ext4 the inode count is fixed at mkfs time. Removing large numbers of small files frees inode entries, allowing new files to be created. This addresses the actual exhaustion reported by df -i and restores the ability to create files.
- ✗
Increase the inode count by running tune2fs -i 0 on the mounted filesystem.
Why it's wrong here
tune2fs -i adjusts the interval between mandatory filesystem checks, not the number of inodes. The inode count is established when the filesystem is created and cannot be increased on a mounted filesystem. This command does not address allocation, so it will not resolve the user's inability to create files.
Visual reference
Go deeper
Related to this question
About these practice questions
Courseiva writes every LPIC-1 question from scratch — 402 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official LPI exam blueprint
This LPIC-1 practice question is part of Courseiva's free LPI certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the LPIC-1 exam.