Linux reports No Space Left on Device even though df -h shows available disk bytes. This is a narrower problem than a complete Linux failure: the most useful evidence is the condition under which it begins.
Define a reproducible test
Primary symptom. Linux reports No Space Left on Device even though df -h shows available disk bytes. Record the precise point of failure and whether the same input, account or connected device succeeds in another supported mode. That working comparison establishes the scope of the repair.
Likely technical explanations
The first hypothesis is a mismatch in the failing path. Compare df -h with df -i on the affected mount point. The second is a lower-level state that the interface may not show: inspect per-filesystem inode exhaustion, reserved blocks and container overlay layers before moving logs. A third possibility is a feature or version limitation, which should be checked against supported documentation before a reset.
For this Linux issue, capture journal timestamps, service unit, kernel version and mandatory access control policy and compare the same service on a non-production machine with matching configuration. Preserve the last known working configuration so you can tell whether a successful retry came from an actual correction or a temporary recovery.
Test outcomes and next actions
| What you observe | What it suggests | Focused response |
|---|---|---|
| Linux reports No Space Left on Device even though df -h shows available disk bytes | The failure affects the specific workflow described here; the entire system is not necessarily broken. | Compare df -h with df -i on the affected mount point. |
| The basic comparison exposes a difference between a working and failing configuration. | A local setting, version, account context or device route deserves attention. | Locate directories containing excessive tiny files and clean only safely identified disposable data. |
| The same failure persists after a reversible correction. | A deeper dependency or compatibility issue may remain. | Inspect per-filesystem inode exhaustion, reserved blocks and container overlay layers before moving logs. |
Before changing anything: Preserve critical data and use vendor-approved drivers or hardware procedures; avoid unsupported firmware changes and destructive testing. Save a screenshot or anonymized log line, record the previous setting, and back up relevant user data. Do not reset every related service just because one test fails.
Choose a recovery route. The Beginner path checks compare df -h with df -i on the affected mount point. The Advanced path investigates inspect per-filesystem inode exhaustion, reserved blocks and container overlay layers before moving logs. They address different evidence; use the path that matches your result.
Step-by-Step Troubleshooting
Choose the Beginner route for reversible checks or Advanced for evidence-driven diagnosis.
Identify the exact failure boundary
Linux reports No Space Left on Device even though df -h shows available disk bytes. Before editing settings, note the exact time, affected account or device, and whether it started after an update, move, hardware change or network change. This is the baseline for the Linux No Space Left on Device Despite Free Disk Space: Check Inodes guide.
Check df -h with df -i on the affected mount point
Compare df -h with df -i on the affected mount point. Observe whether the symptom changes. A clean comparison tells you which part of the process is healthy and avoids unnecessary resets.
Adjust locate directories containing excessive tiny files and
Locate directories containing excessive tiny files and clean only safely identified disposable data. Change only this variable, record its former value, and try the failing action once. If there is no improvement, restore the prior configuration before exploring the Advanced route.
Verify a small file can be created and normal writes resume
A small file can be created and normal writes resume without data loss. Repeat using the same account, network, file, title or hardware condition that previously failed. Do not count a different test as confirmation.
Correlate the failure evidence
Collect the error text or state relevant to Linux No Space Left on Device Despite Free Disk Space: Check Inodes. Record journal timestamps, service unit, kernel version and mandatory access control policy; anonymize account IDs, public IPs and secret-bearing log fragments before sharing.
Inspect per-filesystem inode exhaustion, reserved blocks and
Inspect per-filesystem inode exhaustion, reserved blocks and container overlay layers before moving logs. Record the difference between successful and failed cases and keep the first meaningful error rather than the last cascade message.
df -h; df -iCompare a controlled second condition
Where practical, compare the same service on a non-production machine with matching configuration. If the alternate case works, return to the single configuration difference instead of changing multiple services. Use the vendor-supported method for your current version.
Document the regression test
A small file can be created and normal writes resume without data loss. Leave the previous value documented for rollback, then monitor one normal operating cycle. If symptoms recur, attach the sanitized evidence to a vendor or administrator support request.
Understand the comparison
After the first corrective action, interpret the result carefully. If the original task now works, leave the other settings unchanged. If it still fails, inspect per-filesystem inode exhaustion, reserved blocks and container overlay layers before moving logs. Compare the same service on a non-production machine with matching configuration rather than adding random fixes on top of one another.
For escalation, retain journal timestamps, service unit, kernel version and mandatory access control policy, the original output, and a single before/after comparison. Redact passwords, tokens and personal data. A support agent can then distinguish the same service on a non-production machine with matching configuration from a general outage without repeating risky actions.
Optional targeted diagnostic
Compare free bytes with free inode capacity before deleting any files. Commands below are illustrative and must be run only on systems you are authorized to inspect.
df -h; df -iVerification without guesswork
Pass condition: A small file can be created and normal writes resume without data loss. The validation must exercise the same path that failed originally. A successful settings screen, single ping, application homepage or idle system is not enough if the original failure appears during a different action.
Repeat the test under the original conditions once after a safe relaunch, reconnect or new session. For intermittent failures, record the time and the difference between a clean result and a failed one instead of claiming success from a single attempt.
If the first attempt fails
If the problem persists, restore any test-only settings, preserve the evidence and stop before destructive reset, firmware flash or credential recreation. Give official support the exact symptom, the first failing timestamp and what the comparison established. Preserve critical data and use vendor-approved drivers or hardware procedures; avoid unsupported firmware changes and destructive testing.
Prevent recurrence: Document the working correction: Locate directories containing excessive tiny files and clean only safely identified disposable data. Retain the accepted result (a small file can be created and normal writes resume without data loss) as a future regression test after configuration, software or hardware changes.
Solution Checklist
Questions specific to this fault
How do I know the symptom is actually resolved?
A small file can be created and normal writes resume without data loss. A generic diagnostic test outside the affected workflow is not a substitute.
Should I reset or reinstall everything first?
No. Compare df -h with df -i on the affected mount point. Then choose the smallest supported intervention: locate directories containing excessive tiny files and clean only safely identified disposable data. Preserve recoverable settings and user data.
What should I include in a support request?
Provide the exact failing action, product and version, time, non-sensitive log evidence, and this deeper observation: Inspect per-filesystem inode exhaustion, reserved blocks and container overlay layers before moving logs. Do not include credentials or private customer data.