Recommended Free Tools
Start by identifying whether the filesystem is out of data blocks or inodes: run df -hT and df -i. Then isolate the affected mount with filesystem-bounded du or ncdu, clean only confirmed-safe logs, journals, caches, or unused container data, and investigate open deleted files if df and du disagree. If the data is legitimate and keeps returning, expand the VPS volume rather than repeatedly deleting files.
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
What a 100% disk reading actually means
A Linux VPS reports a disk as full for two different resource limits. The usual case is exhausted data blocks: there is no room for more file contents, temporary files, package downloads, database writes, or log entries. The other case is exhausted inodes, the filesystem records used to represent files and directories. A server can have free gigabytes but still fail to create a file when every inode is consumed.
As an Amazon Associate I earn from qualifying purchases.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Both conditions can produce errors such as No space left on device, failed deployments, package-manager errors, crashed services, and incomplete writes. Do not begin by deleting random files. First establish which mount is full and which resource is exhausted.
First response: confirm the affected filesystem
- Check space by filesystem and type. Run
df -hT. The-hoption makes sizes readable, while-Tshows the filesystem type. Note the mount whoseUse%is 100%; it may be/,/var, a database volume, a Docker data volume, or another mount. A full root filesystem is not the only possible failure. - Check inode consumption separately. Run
df -i. IfIUse%is 100% while byte usage is comparatively low, you have an inode problem and must find excessive numbers of small files rather than merely looking for the largest files. - Record the symptom and timing. Write down whether the failure is a write error, a service crash, a package installation failure, a failed backup, or a deployment that stopped. This helps identify the application that was creating data and prevents you from removing files that are still needed.
- Check the mount before every cleanup command. A directory such as
/var/libmay be on a separate filesystem. Clean the filesystem that is actually full, and do not assume that freeing space under/homewill help a full/varvolume.
Keep a privileged shell available, but avoid starting new services or running large package operations until you have recovered working space. Some emergency commands need a small amount of free space to create temporary files.
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
Find what is consuming the bytes
Use a filesystem-bounded scan so that a mounted backup disk, network share, or container volume does not distort the result.
Start with a one-level directory summary
For a full root filesystem, run:
sudo du -xhd1 /The -x option stays on the filesystem containing the path, -h uses readable units, and -d1 summarizes one directory level. On another mount, replace / with that mount point, for example sudo du -xhd1 /var. Sort or inspect the output and recurse into the largest directory:
Free tools Windows power users keep installed
One-click scans. No signup required.
sudo du -xhd1 /varsudo du -xhd1 /var/lib
Repeat only where the previous result shows meaningful usage. This narrowing approach is faster and less disruptive than scanning every path repeatedly.
Use an interactive view when the tree is complicated
If it is installed, ncdu -x / provides an interactive, filesystem-bounded view. Navigate into the largest directories, but treat deletion prompts as dangerous: the tool can show a path clearly without proving that its contents are safe to remove. Use it to investigate, then apply the owning application’s cleanup procedure.
Inspect the usual high-growth locations
/var/logand application-specific log directories, including web-server and database logs./var/log/journalfor systemd journal files.- Package-manager caches under
/var/cacheand related package directories. - Container storage such as
/var/lib/dockeror the data root configured for another runtime. - Backup, export, upload, and temporary directories created by your applications.
- Database data, write-ahead logs, binary logs, and snapshots, which must be managed through database retention controls rather than manual deletion.
Large files are not automatically expendable. A database file, container layer, or current log may be essential even when it is the largest item on the disk.
Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
Measure and reduce systemd journal usage safely
Measure journal files directly:
sudo journalctl --disk-usageThe systemd manual describes this command as: “Shows the current disk usage of all journal files.” It reports both active and archived journal files, so the number may not equal the size of only the archived files that can be vacuumed.
Rotate, then vacuum archived journals
If your retention policy permits removing older entries, run:
sudo journalctl --rotate
sudo journalctl --vacuum-size=200M--rotate closes the current active journal and starts a new file. Vacuum operations remove archived files; active files can remain, which explains why a subsequent usage report may still be higher than 200 MB. A size limit is a cleanup decision, not a guarantee that total journal usage will never exceed that number.
Choose retention deliberately
Before vacuuming, determine how long you need logs for incident response, security investigations, compliance, or debugging. If a service has its own log rotation, use that mechanism instead of deleting files in its directory. Removing a current log file can leave the process writing to an unlinked inode, creating the very df/du mismatch discussed below.
Review application and web-server logs
After checking the journal, inspect /var/log and each service’s configured log directory. Look for an unbounded debug log, repeated authentication failures, a crashed worker writing a stack trace in a loop, or rotated archives that never expire.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsRank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
- Confirm that log rotation is enabled and that its timer or cron job actually runs.
- Check compression and retention counts; a rotation rule that creates archives without deleting old ones only postpones the problem.
- Use the application’s reload or reopen command after a supported rotation procedure.
- For databases, follow the database vendor’s archive and write-ahead-log retention process. Never remove database log segments by filename guessing.
- For web servers, check access logs, error logs, per-site logs, and any reverse-proxy or application-worker logs.
If one service is growing rapidly, fix its cause—such as a failing upstream, a verbose log level, or a retry loop—after recovering enough space to keep the service stable.
Clean package caches and container data without damaging workloads
Package-manager caches
Inspect package-cache directories and use the package manager’s supported cache-cleaning command for your distribution. A cache can usually be regenerated, but an installed package, a repository metadata file in active use, or a locally stored package needed for an offline recovery may not be disposable. Verify what the command removes before confirming it.
Container images, layers, and logs
Container runtimes can consume space in their data root through old images, stopped containers, writable layers, build caches, and JSON or equivalent container logs. Identify the runtime’s own disk-usage report, then remove only unused objects with its supported prune or cleanup command. Confirm that an image is not needed for rollback and that a stopped container does not contain the only copy of application data.
Do not delete files directly from /var/lib/docker or another runtime data root while the daemon is operating. Manual removal can corrupt metadata, break running containers, or make future cleanup commands unreliable. Keep persistent databases and uploads on deliberate volumes with backups, not inside disposable layers.
When df is full but du cannot find the space
A process can keep an open file after the directory entry has been deleted. The blocks remain allocated until that process closes the file, so df counts the space while du cannot see a pathname for it.
Rank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
List open deleted files with:
sudo lsof +L1Look for a large deleted log or temporary file and note the owning process, user, and file descriptor. Do not truncate or kill a process blindly. Determine whether the service can be reloaded, whether a controlled restart is required, and whether a high-availability or maintenance window is available. Restart or otherwise recycle the owning service using its supported procedure; once the descriptor closes, the kernel releases the blocks. Re-run df -hT and du to confirm recovery.
If a restart is not immediately safe, first free a small amount of space elsewhere, schedule the service action, and monitor the process. A deleted-open file can continue growing while you investigate.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Diagnose inode exhaustion
When df -i shows 100% inode use, search for directories containing millions of small files. Common examples include mail queues, web-session directories, thumbnail or package caches, temporary upload fragments, application work trees, and failed job output.
Use bounded counts to locate concentration without crossing mounts. For example, inspect likely directories with a depth-limited file count and then narrow further:
sudo find /var -xdev -type f | wc -lThis command gives a broad count; repeat it for specific subdirectories rather than launching an unrestricted scan across unrelated filesystems. Once you identify the owner, use the application’s queue-expiry, session-cleanup, cache-pruning, or job-retention feature. Deleting individual files from a live queue or session store can leave inconsistent state even if it frees inodes.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
After cleanup, run df -i again. Byte usage and inode usage are independent, so a successful inode cleanup may barely change the gigabyte figure shown by df -hT.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteDecide between cleanup and expanding the VPS disk
Cleanup is appropriate when the usage is accidental, obsolete, or a one-time surge. Capacity expansion is appropriate when the data is legitimate, recurring, and required by the workload. Compare the choices before taking an irreversible action.
| Decision factor | Cleanup of logs, caches, or unused data | Disk or volume expansion |
|---|---|---|
| Reversibility | Removing a cache is often reversible by regeneration; deleting logs, images, or data may not be. | Usually reversible only by shrinking or restoring a backup, which many filesystems and providers do not support in place. |
| Operational risk | Risk comes from deleting active, required, or compliance-relevant data. | Risk comes from snapshot, partition, filesystem, and provider operations; an error can make the volume unavailable. |
| Time to relief | Can be immediate when a large safe target is identified. | Depends on provider provisioning, partition growth, filesystem growth, and any required reboot or maintenance window. |
| Persistence | Temporary unless retention and monitoring are corrected. | Addresses a genuinely undersized volume but does not stop unbounded logs or caches. |
| Backup requirement | Back up or preserve anything that may be needed before destructive deletion. | Take a provider snapshot or tested backup before resizing. |
| Constraints | Depends on what the application can safely expire. | Provider limits, partition layout, filesystem support, region, plan, and available capacity vary. |
| Recurring cost | Usually no added storage charge, but it requires maintenance. | Creates an ongoing storage cost and may affect the VPS plan or attached-volume limits. |
Safe expansion sequence
- Confirm that growth is legitimate and recurring rather than a runaway log, leak, or failed cleanup job.
- Take a provider snapshot or verified backup and confirm that you can restore it.
- Review the provider’s exact resize procedure, supported filesystems, maximum size, downtime expectations, and billing effect.
- Resize the VPS disk or attach a larger volume through that procedure.
- Grow the partition if the partitioning scheme requires it, then grow the filesystem with the command appropriate to that filesystem. Do not copy a command from another provider or assume that a partition and filesystem expand automatically.
- Verify the result with
df -hT, check application health, and confirm that mounts persist after reboot if a configuration file was changed.
Provider commands, filesystem support, pricing, limits, and downtime differ, so there is no universal Linux resize command that is safe for every VPS.
Make the fix durable
Set journald limits
Configure journal retention in journald.conf or an appropriate drop-in after checking your operational and compliance needs. The documented defaults for SystemMaxUse= and RuntimeMaxUse= are 10% of the relevant filesystem, capped at 4 GiB. SystemKeepFree= and RuntimeKeepFree= default to 15%, also capped at 4 GiB. These are defaults, not a substitute for choosing limits that fit your disk and retention policy.
After changing settings, reload or restart journald according to your distribution’s supported procedure, then verify actual usage with journalctl --disk-usage. Keep enough history to diagnose failures without allowing logs to consume the operating system’s working space.
Keep application rotation working
- Set maximum file sizes, retention counts, and compression in the application or system rotation mechanism.
- Verify that the scheduled rotation job runs and that a new log file receives writes after rotation.
- Alert when a single log grows unusually fast instead of waiting for the disk alert.
Control container growth
Set container log limits supported by your runtime, review image and build-cache retention, and schedule pruning of objects that are confirmed unused. Monitor the runtime data root separately from the root filesystem when it is on its own mount.
Monitor both bytes and inodes
Create alerts below 100% for every important mount. Track df -hT-style byte utilization and df -i-style inode utilization; alerting on only one misses the other failure mode. Include trend views so you can distinguish a sudden incident from a steady workload that needs more capacity.
Review temporary files, backups, and database retention
Schedule reviews of temporary directories, export files, local backups, package caches, and database archives. Keep tested backups or snapshots before destructive cleanup and before filesystem resizing. A backup that has never been restored is not proof that recovery will work.
Quick Recap
A concise emergency runbook
- Run
df -hTanddf -i; record the full mount and whether bytes or inodes are exhausted. - Use
sudo du -xhd1 <mount>orncdu -x <mount>to locate the largest branches. - Measure journals with
sudo journalctl --disk-usageand review system, web, application, and database logs. - Apply supported rotation, vacuum, cache cleanup, or container-pruning actions only to confirmed-safe targets.
- If visible files do not explain
df, runsudo lsof +L1and recycle the owning service in a controlled window. - If inodes are full, locate directories with excessive small files and use the owner application’s cleanup process.
- Re-run both
df -hTanddf -i, then verify that failed services, writes, and package operations recover. - If legitimate growth will continue, snapshot or back up the VPS and expand the volume using the provider- and filesystem-specific procedure.
Common mistakes that make a full disk worse
- Deleting by guesswork: removing files from database, container, queue, or runtime directories can destroy state.
- Scanning without
-x: crossing into other mounts leads to the wrong conclusion and wastes time. - Assuming
duis authoritative when files are open and deleted: uselsof +L1for the mismatch case. - Vacuuming without checking retention needs: old journal entries may be required for an incident investigation.
- Restarting a critical service without a plan: recycle the process only through a controlled maintenance or failover procedure.
- Resizing without a backup: provider and filesystem operations can fail, and shrinking is often unsupported.
- Fixing the symptom only once: without rotation, limits, alerts, and retention controls, the same full-disk incident will return.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
