Check bytesByte pressure means the filesystem has little storage space left. df -h shows Use% and available space.
Storage repair
Linux Disk Space and Logs for Makers
Learn how bytes, inodes, logs, and deleted-open files can each make a project machine look full.
Ladder steps
Each step should prove one idea before the project asks for the next one.
Check inodesInode pressure means too many files exist even if bytes look available. df -i shows IUse%.
Check logs and journalsLogs can grow until they dominate a filesystem. journalctl --disk-usage gives the journal size.
Check deleted-open filesA deleted file can still consume space until the process closes it. lsof +L1 lists open deleted files.
Examples to inspect
Use examples to read signals, not as blind recipes.
Check filesystem byte usage
df -hExpected signal: Use% and Available columns
Check inode usage
df -iExpected signal: IUse% column
Find deleted-open files
sudo lsof +L1Expected signal: Open files with link count below one
Caution: May expose process paths; inspect before sharing output.
Common traps
- Deleting random files before proving the owner.
- Ignoring inode pressure.
- Deleting journal directories manually.
Practice task
Write a five-command disk-full triage checklist and explain what each command proves.
Next steps
- Use the LinuxOneLiners disk-full hub.
- Learn log search.
- Learn Docker disk usage.
Practice ladder
- Near-Copy Rebuild: Recreate one example, decision path, or worked explanation from Linux Disk Space and Logs for Makers. Keep most givens the same, then apply, explain, and check while naming each cue you used. Use the lesson's example block when it helps.
- One-Change Transfer: Change exactly one condition, number, input, symptom, material, or constraint from the near-copy case. Then apply, explain, and check again and explain what changed.
- Mixed Review Set: Interleave this topic with one prerequisite or adjacent idea. Write three short prompts: one recall, one application, and one comparison.
- Find And Fix The Error: Invent a plausible wrong answer, unsafe step, invalid assumption, or bad classification. Mark the first point where it goes wrong, then correct it using the lesson's check.
Flashcard preview
How can df -h look fine while a filesystem is still unusable?
The filesystem can be out of inodes; check df -i.
What does the 'Check bytes' step prove?
Byte pressure means the filesystem has little storage space left. Check: df -h shows Use% and available space.
What does the 'Check inodes' step prove?
Inode pressure means too many files exist even if bytes look available. Check: df -i shows IUse%.
What does the 'Check logs and journals' step prove?
Logs can grow until they dominate a filesystem. Check: journalctl --disk-usage gives the journal size.
What does the 'Check deleted-open files' step prove?
A deleted file can still consume space until the process closes it. Check: lsof +L1 lists open deleted files.
When would you use `df -h`?
Use it to check filesystem byte usage. Expected signal: Use% and Available columns
Downloadable study pack
Export the same ladder as a plain Markdown note or Anki-compatible TSV. Commands and code blocks stay plain so they work in local notes.
Related paths
Study pack check passed. Notes, cards, examples, and practice tasks are meant to keep the ladder useful outside the page.
Continue learning this topic
Use this page as part of a project path, not as a one-off article. Save the note, review the cards, try the practice task, then choose the next ladder based on what your project exposes.
Study assets
Project context
- Deploy a Static Site on a VPS
- Browse Software and Linux
- Next ladder clue: Use the LinuxOneLiners disk-full hub.
Related references
Buy me a coffee for more maker ladders
TopicLadder is free to read. Support helps turn rough project paths into useful notes, cards, videos, and practice tasks.