LPIC-1 Devices, Filesystems and FHS Practice Question
A user complains that a filesystem is reporting 'Disk quota exceeded' even though the user has not stored any new files recently. What could be the cause?
⚠ Common exam trap
Many candidates assume 'Disk quota exceeded' always refers to disk space (blocks), but LPIC-1 tests the distinction between block quotas and inode quotas, and that the same error message applies to both.
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
✓
The user has exceeded the inode quota
Linux filesystems enforce two types of quotas: block quotas (for disk space) and inode quotas (for the number of files and directories). If the user has not stored new files recently but still receives a 'Disk quota exceeded' error, it is likely that they have exceeded their inode quota, meaning they have created too many files or directories (each consuming an inode), even if those files are small or empty. The error message is generic and can refer to either quota type, so the inode limit is the probable cause when no recent data writes have occurred.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Symlinks are counted against the quota
Why it's wrong here
Symlinks are not counted against quotas; they are inodes pointing to other files. The likely cause is another process or user writing into the same quota-limited filesystem, or inode quota exhaustion from many small files.
- ✗
Hard links are consuming additional inodes
Why it's wrong here
Hard links share the original file's inode, so they add no inode consumption; the quota breach comes from inode exhaustion by many small files or block usage. Hard links are tempting because they genuinely allow one file to appear in multiple directories without duplicating data.
- ✓
The user has exceeded the inode quota
Why this is correct
Disk quotas limit both blocks and inodes separately. A user can stay under the block quota yet exceed the inode quota by creating many small files or directories, so writes fail with 'Disk quota exceeded' despite no significant new data being stored.
- ✗
File ownership is misconfigured
Why it's wrong here
Quota accounting tracks blocks and inodes consumed by a user's files, not ownership metadata, so misconfigured ownership does not itself trigger the exceeded message. It is tempting because ownership errors cause access problems, but quota enforcement keys on the user ID owning the files, not on whether that ownership is correct.
Go deeper
Related to this question
About these practice questions
This LPIC-1 question is part of Courseiva's 402-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.