← 문제 라이브러리
Linux Beginner LINUX-001 · 16 min

An inode problem where files cannot be created even though disk space is free

A problem for identifying and organizing inode exhaustion, which is easy to miss when looking only at df output.

무료
시나리오

A batch job created hundreds of thousands of temp files, so the service prints 'No space left on device', yet df -h shows plenty of disk capacity. The operator must not mistake this for a capacity problem and instead quickly identify inode exhaustion.

먼저 볼 것
  • Identify the primary failure signal in the CLI Drill scenario.
  • Separate visible symptoms from the underlying technical dependency.
  • Describe the safest recovery path and the follow-up prevention work.
점검 체크리스트
  1. Summarize the current impact and the last known change.
  2. Collect direct evidence from logs, runtime state, and configuration before changing anything.
  3. Separate immediate recovery from permanent prevention work.
복구와 재발 방지

Choose the smallest safe recovery action first, then record the prevention work that reduces repeat incidents.

같이 보면 좋은 질문
Why can file creation fail even when disk space looks available?

The filesystem may be out of inodes, so metadata allocation fails even though block usage still looks healthy.

What is the right cleanup mindset here?

Find the tiny-file growth pattern first, then clean the source safely instead of deleting files blindly.