Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

VPS & Linux

Linux inode exhaustion: why free disk space can still mean no space left

Published August 2026 · 2 min read · Updated 2026-09-05

A filesystem can report free gigabytes and still reject new files when it runs out of inodes. Inode exhaustion is common with caches, sessions, mail queues, tiny generated files, dependency trees, and forgotten temporary directories.

Confirm blocks versus inodes

Use df for block capacity and df -i for inode usage on the affected filesystem. A “no space left on device” error can mean either resource is exhausted.

Check the mount that actually backs the failing path. Containers, separate /var or /home filesystems, and bind mounts can hide which filesystem is full.

Find directories with extreme file counts

Count files by directory and narrow the search progressively. Avoid an expensive full-filesystem recursive scan during an incident. Caches, sessions, thumbnails, spool directories, package trees, and application temp files are common sources.

Understand whether files are disposable before deleting them. A mail queue or database directory is not a cache just because it contains many small files.

Fix the lifecycle that created the files

Add expiration, rotation, queue processing, cache cleanup, or application retention so the same directory cannot grow forever. Monitor both disk bytes and inode percentage because either can become the first limit.

If the workload legitimately needs huge file counts, filesystem layout and service design may need to change so emergency cleanup is no longer part of normal operation.

Recover cautiously under full conditions

Free a small known-safe amount first so services can create state again, then perform controlled cleanup. Verify application queues, uploads, logging, and package operations after recovery.

  • Check df and df -i.
  • Locate the high-file-count path.
  • Delete only data with a known lifecycle.
  • Add inode monitoring and retention.

Next step

Diagnose inode exhaustion by filesystem, find directories creating huge file counts, and clean up safely without confusing inode use with byte capacity.

Explore DotMoose VPS hosting

Keep reading

Related guides.

HTTP 500, 502 and 503 errors explained for website owners

Learn what HTTP 500, 502 and 503 errors usually indicate, which layer to investigate, what evidence to collect, and when restarting a service is not the real fix.

Read the guide

Linux file permissions: ownership, modes, groups and ACLs explained

Understand Unix ownership and rwx modes, then use groups and ACLs where needed so services can access files without opening them to every user.

Read the guide

Moving a DreamHost VPS to Canadian hosting

Inventory the server, copy it safely, test it, and cut DNS over with a rollback plan.

Read the guide

More vps & linux guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move