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 disk cleanup: free space without deleting the wrong data

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

Disk cleanup should begin with ownership and lifecycle, not a blind delete command. The safest space to reclaim is data you can name, reproduce, rotate, or expire without destroying the only copy of something important.

Identify the full filesystem and largest consumers

Confirm the mount with df, then use du or filesystem-specific tooling to find large directories. Account for deleted-but-open files, snapshots, container layers, package caches, logs, databases, uploads, and backup files stored on the same disk.

A large directory is not automatically safe to remove. Record what service owns it before changing anything.

Look for deleted files still held open

A rotated or manually deleted log can continue consuming blocks while a process keeps the old file descriptor open. lsof-style checks can reveal this mismatch between directory listings and filesystem usage.

Restart or reopen the specific service only after confirming the file can be released safely.

Clean by policy, not panic

Use logrotate, package-cache cleanup, temp-file policies, application retention, image pruning, or explicit artifact expiration as appropriate. Keep independent backups off the live filesystem. Do not accumulate “backup” archives beside production data.

Do not remove database, queue, mail, or application state because a directory name looks temporary.

Prevent the next full disk

Set alerts before the filesystem reaches emergency levels, track growth rate, reserve operational headroom, and document which directories are expected to grow. Resize storage when retained production data legitimately outgrows the plan.

  • Confirm the exact mount.
  • Check deleted-open files.
  • Apply service-specific retention.
  • Alert before emergency capacity.

Next step

Find what is consuming disk space, check logs, packages, caches and application data, then reclaim capacity with a rollback-aware cleanup plan.

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