22
submitted 1 year ago by keenworld@midwest.social to c/linux@lemmy.ml

I've had an Ubuntu 22.04 setup going for around a year, and over that year I've had to increase the size of the partition holding my /var folder multiple times. I'm now up to 20GB and again running into problems, mainly installing new apps, because that partition is again nearly full. I've used commands sudo apt clean and sudo journalctl --vacuum-size=500 to temporarily clear up some space, but it doesn't take long to fill back up, and gets less effective with time, til I have no choice but to expand the partition again.

Am I doing something wrong? Is it normal to need 20GB+ for var? Is there a way to safely reclaim space I don't know about?

all 24 comments
sorted by: hot top controversial new old
[-] SeeJayEmm@lemmy.procrastinati.org 11 points 1 year ago* (last edited 1 year ago)

We can't really help until you tell us what's using the space. Could be databases, could be docker, could be logs.

I use... du -xh --max-depth 2 /var/ | sort -h

[-] pnutzh4x0r@lemmy.ndlug.org 11 points 1 year ago* (last edited 1 year ago)

If you suspect that the issue is journald, you can use the following command to check how much space it is using:

journalctl --disk-usage

Rather than periodically running journalctl --vacuum-size=500 to free up space, you can just limit the journal by adding the following to a new file such as /etc/systemd/journald.conf.d/size.conf:

[Journal]
SystemMaxUse=512M

This will limit the journal from using more than 512MB. That said, if journald is filling up fast, then something is spamming your logs and you could run journalctl -a -f to get a sense of what is being written to your logs.

[-] jflesch@lemmy.kwain.net 7 points 1 year ago* (last edited 1 year ago)

You can use du -sh to figure out what's using most of the space. Something along the line of:

sudo -i
du -sh /home /usr /var
du -sh /var/*
du -sh /var/log/*
# etc

If it's one of your log files (likely), you can run something like tail -n 100 /var/log/[culprit] or tail -F /var/log/[culprit] to see what is being flooded in this log file exactly. Then you can try to fix it.

[-] Justin@apollo.town 6 points 1 year ago

Install ncdu, then sudo ncdu -x /var it'll tell you what is taking up space, then if you tell us, we can help you identify how to minimize it and keep it low.

[-] drwho@beehaw.org 5 points 1 year ago

There's a way to figure out what is responsible for using up all of that space. A couple of ways, really. Here's the one I use, though: du -s -h -x /path/to/ | sort -h -r | head -n 10*

  • du
    • -s - display only a total for each argument
    • -h - human readable values
    • -x - do not cross file systems (in case you have another directory tree mounted under /var, which'll complicate figuring out what's in there for this purpose)
  • sort
    • -h - compare human readable numbers (e.g., 1G, 2T)
    • -r - reverse sort (biggest first)
  • head
    • -n 10 (first ten lines or less)
[-] example@reddthat.com 5 points 1 year ago

ncdu makes it even easier if you want to interactively browse through folders to see which files exactly are eating up space

[-] orsetto@beehaw.org 5 points 1 year ago

There's probably some program that's filling up /var/log. Check that directory.

[-] phx@lemmy.ca 5 points 1 year ago

If I had to guess, I'd say it's probably snaps. I've had the same issue and they've slowly been taking up more and more of my space, often with new gnome snaps being installed but the old ones not removed.

Try "snap list" to see what's installed as snap

[-] tychosmoose@lemm.ee 4 points 1 year ago

See what's using the space. This will list any dirs using >100MiB:

sudo du -h -d 5 -t 100M /var

[-] foonex@feddit.de 2 points 1 year ago

Do you know what takes up the space? Something like gdu or ncdu will help you analyze the problem.

[-] pewpew@feddit.it 2 points 1 year ago* (last edited 1 year ago)

I had the same problem on my PC. Journald was spamming PCI errors all the time and the disk was filling up quite quickly. I ended up disabling journald and rsyslogd and the problem was fixed. You can delete the log files, if you find them

[-] db2@sopuli.xyz 1 points 1 year ago

and the problem was fixed

Umm...

[-] oleorun@lemmy.fan 6 points 1 year ago

This is how my friend fixed her check engine light. Just put the official Car Talk electrical tape over it and problem solved.

[-] GoodNewsEveryone@lemmy.ca 2 points 1 year ago

And the problem was fixed. FIXED. No more error logs.

[-] jsveiga@sh.itjust.works 1 points 1 year ago

What is the filesystem type? If it's btrfs, maybe it's the snapshots.

[-] redcalcium 1 points 1 year ago

Are you using docker? If so, you need to prune dangling images and volumes from time to time because they're not automatically deleted.

[-] wewbull@feddit.uk 1 points 1 year ago

Are you using docker on BTRFS?

Docker makes use of BTRFS snapshots, but it snapshots the whole volume. That means as other programs delete/rewrite files, the old copies still exist in the snapshot. I've ended up putting /var/lib/docker on it's own filesystem.

[-] axum@kbin.social -2 points 1 year ago

20gb for a Linux workstation is embarrassingly tiny in 2023.... Hell it's barely passable for a phone

this post was submitted on 05 Aug 2023
22 points (92.3% liked)

Linux

47343 readers
1382 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS