Crashes, 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 minuteWindows 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 reinstalliTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
To free disk space safely, first identify the full filesystem, then determine whether systemd’s journal is responsible. Use df -hT and du -xhd1 to locate the pressure, inspect journald with journalctl --disk-usage, rotate active journal files, and vacuum them with an explicit age, size, or file-count limit. Verify the result with df -hT, check for deleted files still held open, and set journald’s free-space and retention policy so the problem does not return.
Why Linux log files consume a full disk
Linux servers commonly write several different kinds of logs. The systemd journal stores service, kernel, boot, and other system messages. Traditional text logs may be written under /var/log by the operating system or by individual services. Applications and container runtimes can maintain their own files and retention rules.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
These sources are independent. Vacuuming the journal cannot reclaim space used by an application log or a container-runtime log, and deleting a text log does not reduce journal usage. Start by measuring the filesystem and locating the largest directories instead of assuming that /var/log/journal is the cause.
A full filesystem can affect much more than logging. Services may fail to write state, package updates can stop, databases may reject new transactions, and troubleshooting commands may produce incomplete output. Treat cleanup as a controlled capacity-recovery operation: measure first, preserve information that may be needed, make one bounded change, and measure again.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application: attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.
Measure the full filesystem before deleting anything
Record the current state so you can distinguish a successful cleanup from a change elsewhere on the host.
df -hT
sudo du -xhd1 /var 2>/dev/null | sort -h
sudo du -xhd1 /var/log 2>/dev/null | sort -h
Read the filesystem report
df -hT reports each mounted filesystem, its type, total capacity, used space, available space, and percentage used. The mount point with little available space is the one that needs investigation. A server can have plenty of capacity on one mount and still fail writes because another mount is full.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsLook at the mount point rather than only the total across the machine. If /var or /var/log is a separate mount, its available space can be exhausted while the root filesystem still appears comfortable. Record the percentage and available amount before cleanup, then use the same command afterward so the comparison is like-for-like.
Use du -x to stay on the same filesystem
The -x option prevents a mounted filesystem beneath the path from being counted as part of its parent. That matters on hosts where directories such as /var contain separate mounts. The two du commands show which immediate directories dominate /var and then /var/log; sort -h orders the results by human-readable size.
Do not change files based on a single directory listing. Compare the largest directory with the mount that df identified, and note whether the space is in the journal directory, ordinary text logs, application data, or another location. The 2>/dev/null redirection keeps permission warnings from obscuring the size ranking; it does not make inaccessible data disappear from the filesystem.
Check whether journald is the main consumer
When the journal appears to be responsible, inspect it before choosing a retention rule.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →sudo journalctl --disk-usage
sudo journalctl --list-boots
sudo journalctl -p warning..alert -b
What each command tells you
journalctl --disk-usagereports the space used by the journal’s active and archived files. It is the journal-specific measurement to compare before and after cleanup.journalctl --list-bootslists boots represented in the journal, helping you see how much historical boot context may be useful during troubleshooting.journalctl -p warning..alert -bdisplays warning-through-alert messages from the current boot. Review this output before reducing retention if the host is already experiencing a service or hardware problem.
There is no universal amount of space that journald will free on every server. Savings depend on the host’s message rate, existing files, filesystem size, and configured policy. The commands provide measurements for this machine rather than a promised disk-savings figure.
The distinction between active and archived data is important. An active journal file is still being written; archived files are the ones that age and become eligible for vacuuming. Therefore, a large total does not by itself prove that all of that total can be removed immediately.
Choose an explicit journal-retention rule
Use a rule that matches the evidence and retention obligations for the server. The journal supports three different vacuum bounds:
| Option | Example | What it limits | When it is useful |
|---|---|---|---|
--vacuum-time= |
--vacuum-time=30d |
Removes the oldest archived journal files outside the selected age window. | An age-based rule is straightforward to explain to investigators and operations staff. |
--vacuum-size= |
--vacuum-size=500M |
Removes the oldest archived files until their archived usage is below the specified size. | A size ceiling gives storage planning a predictable bound. |
--vacuum-files= |
--vacuum-files=5 |
Retains only the selected number of archived journal files. | A file-count limit is simple, but it does not guarantee a byte limit because files can differ in size. |
The systemd manual describes the size behavior this way: “–vacuum-size= removes the oldest archived journal files until the disk space they use falls below the specified size.” Each option acts on archived files, so select a period, byte ceiling, or file count that still preserves logs required for incident response, security review, or compliance.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
Age and size answer different operational questions. An age rule makes it easy to state that a defined period of history remains available, while a size rule makes capacity planning easier because archived usage has a ceiling. A file-count rule can be useful where the number of journal segments matters, but segment sizes vary, so it should not be treated as a storage guarantee.
You can document the decision alongside the server’s operating procedure: identify the selected bound, the reason for it, the person or team responsible for approval, and the measurement that will be checked afterward. This avoids an emergency operator choosing a value without knowing the host’s evidence requirements.
Safely reclaim journal space
Rotate first, then vacuum. Rotation archives the currently active journal files; systemd documents that combining --rotate with a vacuum option gives the operation its greatest effect.
Keep archived data from the last 30 days
sudo journalctl --rotate
sudo journalctl --vacuum-time=30d
This is an age rule, not a promise that every message older than 30 calendar days disappears immediately. The command removes eligible archived files according to the journal’s file boundaries and available data. If most usage is in the newly active file, the immediate reduction can be smaller than expected.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Cap archived journal data at 500 MiB
sudo journalctl --rotate
sudo journalctl --vacuum-size=500M
The 500 MiB figure is an example policy. Choose another value when your filesystem size, message volume, and evidence requirements call for it. The bound applies to archived journal data, not to every byte that --disk-usage can report.
Retain five archived files
sudo journalctl --rotate
sudo journalctl --vacuum-files=5
A file-count policy can retain substantially more or less data than expected when individual files vary in size. Use it only when counting files is more meaningful for your operational requirement than measuring age or bytes.
Do not use unbounded deletion during an incident
A command that indiscriminately removes log files can destroy evidence needed to diagnose the outage or investigate a security event. Before reducing retention, identify the minimum period your organization requires and preserve any logs already needed by responders. Use the journal’s explicit vacuum bounds rather than an unbounded deletion command.
If an incident is active, capture or forward the relevant records before cleanup when your procedures require it. Review the current-boot warning-through-alert output and the boot list so that a hurried cleanup does not erase the context responders are using. Record the selected bound and the time of the operation in the change or incident record.
Verify reclaimed space and account for open files
Measure both the journal and the filesystem after the operation.
sudo journalctl --disk-usage
df -hT
sudo lsof +L1
Why the journal number may not match the target
It is normal for journalctl --disk-usage to remain above a requested vacuum size immediately after cleanup. The usage total includes active files, while vacuum removes archived files. Rotating first moves the current active file into the archived set so that more data can become eligible, but a newly active file still contributes to the reported total.
Rank #3
- 【Large size】:Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】:Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】:Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
Do not interpret a remaining total as proof that the command failed. Compare the before-and-after values, check whether archived files were actually present, and compare the filesystem’s available space. If the target concerns archived data, the total reported by the command is intentionally a broader number.
Find deleted files that still consume blocks
lsof +L1 lists open files whose directory entries have been deleted. A process can continue writing to such a file, keeping its blocks allocated even though the filename no longer appears in a directory listing. The output identifies the owning process and service. Restart that service only through your normal change-control procedure, because a restart can interrupt traffic or other work.
If df -hT shows recovery but a process continues to hold a large deleted file, coordinate a controlled restart and then run the measurements again. If no deleted-open files appear, continue investigating the directories that du identified. This check is especially useful when a log was removed manually but the writer has not closed its file descriptor.
Prevent journald from filling the disk again
One-time vacuuming treats the symptom. A journald policy controls how much space the journal may consume and how much room it must leave for other uses.
Inspect the active configuration
sudo grep -RInE '^(SystemKeepFree|RuntimeKeepFree|SystemMaxUse|RuntimeMaxUse|MaxRetentionSec|MaxFileSec)=' /etc/systemd/journald.conf /etc/systemd/journald.conf.d 2>/dev/null
sudo systemctl cat systemd-journald
The first command searches the main configuration file and drop-in directory for the relevant settings. The second shows the systemd unit definition in use on the host. Keep the configuration review tied to the filesystem where the journal actually resides; a policy that is appropriate for a large dedicated mount may be unsuitable on a small root filesystem.
Review both the main file and drop-ins because an override in the drop-in directory can change the effective policy. Preserve a copy of the current values in the change record before editing, then verify the resulting values after the normal configuration-application procedure.
Understand the free-space controls
SystemKeepFreetells journald how much space to leave free on the filesystem used for persistent system journals.RuntimeKeepFreetells journald how much space to leave free for runtime journals.SystemMaxUseandRuntimeMaxUseprovide maximum-use limits for persistent and runtime journal storage.MaxRetentionSecandMaxFileSecaffect retention duration and file rotation behavior when configured.
SystemKeepFree and RuntimeKeepFree are specifically intended to reserve space for other uses. Set values that leave enough room for the operating system, application writes, updates, and emergency diagnostics while honoring your required log-retention period.
Free-space reservations and maximum-use limits serve different purposes. A reservation protects headroom for other writers; a maximum limits the journal’s own footprint. Consider both when selecting a policy rather than relying on only one setting. A retention limit can preserve history but still permit an unsuitable amount of storage on a small filesystem, while an aggressive maximum can shorten the available history.
Apply a policy through change control
Edit the appropriate configuration file or drop-in using your organization’s standard process, document the reason and selected bounds, and apply the change in the way supported by the distribution. A controlled systemctl restart systemd-journald may be required, but the exact reload or restart behavior should be verified for the host before execution. After the next rotation cycle, rerun journalctl --disk-usage and df -hT to confirm that the policy leaves the expected headroom.
Do not choose a retention period solely because it is convenient. A shorter policy reduces storage pressure but can remove historical context; a larger policy preserves more evidence but requires capacity planning and monitoring. Recheck after a rotation cycle, because the policy’s effect is evaluated as files rotate and age rather than only at the instant the configuration is edited.
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
When the journal is not the problem
If journalctl --disk-usage is small compared with the full filesystem, stop vacuuming journald and return to the directory measurements. Inspect the largest ordinary text-log directories, application-specific log paths, and container-runtime storage separately.
- Traditional text logs may have their own rotation and compression configuration.
- Applications may write outside the usual
/var/loghierarchy and may expose their own retention settings. - Container runtimes can retain logs independently of systemd’s journal, depending on the runtime and logging driver.
These policies are implementation-specific. Identify which service owns a large file, consult that service’s supported rotation or retention mechanism, and preserve any data required for operations or compliance. Do not repeatedly vacuum the journal when another owner is consuming the space.
Use the same measurement discipline for these other owners: identify the mount, locate the directory, determine which service writes the files, and learn that service’s supported rotation or retention controls. Avoid deleting a file while its writer is active unless the service’s documented procedure permits it; an open deleted file can continue consuming blocks and may require a controlled restart to release them.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshoot common cleanup outcomes
The filesystem is still full after vacuuming
- Run
df -hTagain and confirm which mount remains full. - Run the two
du -xhd1commands to see whether the largest directory is outside the journal. - Run
sudo lsof +L1to find deleted files held open by running processes. - Inspect application and container logs if the journal is not the dominant directory.
Also compare the journal’s before-and-after values with the filesystem’s available space. The journal total may stay relatively high because active files remain, while another directory may have been the source of the full-mount condition all along.
The vacuum reports little or no reduction
Check whether the journal has enough archived data older than the selected bound. A size target cannot remove data that is already below the target, and an age target cannot remove files still within the retention period. If active files dominate the usage total, run sudo journalctl --rotate before repeating the selected vacuum command.
A file-count target can likewise appear to do little when the number of archived files is already at or below the requested count. Confirm the selected option and value, and do not switch to an unbounded deletion command simply because the first bounded operation produced little visible change.
Space returns quickly
Compare the timestamps and sizes of the largest files after a short observation period, subject to your operational policy. A noisy service, a failing device, or an application emitting repeated errors can regenerate logs rapidly. Use journalctl -p warning..alert -b to review high-priority messages from the current boot, then investigate the responsible service rather than continually deleting its output.
Rapid recurrence is a signal to fix the producer or adjust a documented policy, not merely to repeat vacuuming. Keep enough history to establish when the messages began and what changed, while ensuring the selected free-space settings reserve room for normal operation.
Recommended Free Tools
Retention conflicts with an investigation
Pause destructive cleanup, preserve the logs requested by responders, and obtain the required approval before changing the retention rule. A full disk is an operational emergency, but removing evidence without authorization can create a separate security or compliance incident. If immediate recovery is unavoidable, document the commands, bounds, time, and resulting measurements.
Operational checklist
- Identify the full mount with
df -hT. - Locate large directories with
du -xhd1 /varanddu -xhd1 /var/log. - Measure journald with
sudo journalctl --disk-usage. - Review boots and high-priority current-boot messages before reducing retention.
- Choose an age, size, or file-count rule that meets evidence requirements.
- Run
sudo journalctl --rotate, then the selected bounded vacuum command. - Verify with
journalctl --disk-usageanddf -hT. - Check
sudo lsof +L1for deleted files still held open. - Inspect application, text-log, and container-runtime owners when journald is not the main consumer.
- Set and review
SystemKeepFree,RuntimeKeepFree, and appropriate retention limits through change control. - Record the selected bound, before-and-after measurements, and any service restart in the incident or change record.
Frequently Asked Questions
What is the safest first command when a Linux server is out of space?
Run df -hT to identify the full mount, then use sudo du -xhd1 /var 2>/dev/null | sort -h and the equivalent /var/log command to locate the largest directories. Measure before deleting anything.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
How do I see how much space systemd’s journal uses?
Run sudo journalctl --disk-usage. The total includes both active and archived journal files, so it may be larger than the amount eligible for immediate vacuuming.
Should I rotate the journal before vacuuming it?
Yes. Run sudo journalctl --rotate first, then the selected bounded vacuum command. Rotation archives active files, and systemd documents that combining rotation with vacuum has the greatest effect.
Why is journal usage still above my 500M vacuum target?
Vacuum options remove archived files, while --disk-usage counts active and archived files. A newly active file still contributes to the reported total, so the figure does not necessarily fall to the requested number immediately.
Is it better to vacuum by age, size, or file count?
Use age when you must preserve a clearly stated period, size when you need a predictable storage ceiling, and file count only when the number of archived files is the meaningful operational limit. File count does not guarantee a byte ceiling.
Can I delete everything under /var/log to recover space?
Avoid unbounded deletion. Logs may be needed for outage diagnosis, security review, or compliance. First identify the owning service and use an explicit retention or vacuum bound that preserves the required history.
What if journald is not using much space?
Stop vacuuming the journal and inspect ordinary text logs, application-specific paths, and container-runtime logs. Their rotation and retention policies are independent of journald and must be handled by the relevant owner.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →What does lsof +L1 show after log cleanup?
It lists open files whose directory entries were deleted. A process can keep writing to such a file and retain its disk blocks. Identify the owning service and perform any restart through normal change control.
How do I keep journald from filling the disk again?
Review SystemKeepFree, RuntimeKeepFree, SystemMaxUse, RuntimeMaxUse, MaxRetentionSec, and MaxFileSec in the journald configuration and drop-ins. Set free-space and retention limits appropriate to the filesystem and evidence requirements, then verify after a rotation cycle.
The Bottom Line
Measure first, identify the actual log owner, rotate active journals, and vacuum only with an explicit age, size, or file-count bound. Verify both journal and filesystem usage, check for deleted files still held open, and configure journald’s free-space and retention controls so emergency cleanup does not become routine.
Quick Recap
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.
Recommended Free Tools

