why would var have such a restraint? reminds me of overly complex tutorials tricking people into elaborate partitioning schemes
this post was submitted on 21 Sep 2025
24 points (100.0% liked)
Linux
58470 readers
538 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
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 6 years ago
MODERATORS
/var is often where processes dump a lot of data (logs, databases, etc), and subpartitioning of /var sets a cap so that when too much data is dumped there, the application crashes instead of the whole system. /var/log is often recommended to be subpartitioned separately as well, so that logging can still go on if the application data fills up and crashes.
These kinds of overruns can be intentional DOS attacks, also, so the subpartitioning is often a security recommendation. NIST 800-171 requires separate partitions for /var, /var/log, /var/log/audit, and /var/tmp
Uninstall all the flatpak packages that are installed as system wide packages and install them as user packages, that way flatpak will use your /home partition. I had the same problem.
Uninstall all the flatpak packages that are installed as system wide packages and install them as user packages
would you eli5 how to do this?
du -hsc /var
Check the sheets to see which directories are taking up your space.
du -hsc /var
sudo du -hsc /var returns: 10G /var, 10G total
du -hsc /var returns: du: cannot read directory '/var/lost+found': Permission denied, du: cannot read directory '/var/spool/cron/crontabs': Permission denied...
25 more lines like this
Put a sudo in front of that then
apt-get clean will clear the apt cache and should give you enough temporary storage headroom on /var to do things, but if you're bumping up on this limit often, you'll need to reconfigure your storage.
Usually var gets full of old log files. So maybe delete some of those. Apt-cache is also a suspect
Well, what's using your /var?
You can use baobab or ncdu to try to figure out what's filling it up.
I installed baobab 48.0.2 with sudo apt.
should I install ncdu 2.9.1 with uniget install ncdu? the apt version is older than that
You do you, but I think it's rarely worth it having the absolutely newest version of something. The Debian version of a package may be older, but often has the advantage of being well-tested. And the Debian version of ncdu is all I've ever used and it has worked well.
uniget, huh? That's not a package manager I've ever heard of before.