[SOLVED] too many unsuccessful flatpak updates lingered in this directory. It sorted itself out after rebooting the system.
var capacity 11.1 GiB, var usage 10.6 GiB
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.
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
why would var have such a restraint? reminds me of overly complex tutorials tricking people into elaborate partitioning schemes
/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
dd if=/dev/zero of=/var
But really, remove what you don’t use and/or stop using flatpak.
FYI Don’t use this command. I think it was intended as a joke, but I just want to clarify.
That’s why I didn’t include any privilege escalation, even if someone ran it as is it would fail. But a warning is also appropriate, thanks.
That doesn’t make it better.
The first thing a novice user learns is to slap
sudo
in the front if they don’t have access to do something.Nobody puts var on its own partition anymore, it would sill fail.