[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

all 21 comments

sorted by: hot top controversial new old
[–] 14 points 10 months ago (1 child)

why would var have such a restraint? reminds me of overly complex tutorials tricking people into elaborate partitioning schemes

  • source
  • hideshow 2 child comments
  • [–] 5 points 10 months ago* (last edited 10 months ago)

    /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

  • source
  • parent
  • [–] 10 points 10 months ago* (1 child)

    du -hsc /var

    Check the sheets to see which directories are taking up your space.

  • source
  • hideshow 2 child comments
  • [–] [S] 1 point 10 months ago* (1 child)

    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

  • source
  • parent
  • hideshow 2 child comments
  • [–] 10 points 10 months ago* (1 child)

    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.

  • source
  • hideshow 2 child comments
  • [–] 4 points 10 months ago

    Well, what's using your /var?

  • source
  • [–] 4 points 10 months ago

    Usually var gets full of old log files. So maybe delete some of those. Apt-cache is also a suspect

  • source
  • [–] 3 points 10 months ago (1 child)

    You can use baobab or ncdu to try to figure out what's filling it up.

  • source
  • hideshow 2 child comments
  • [–] [S] 1 point 10 months ago (1 child)

    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

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 10 months ago

    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.

  • source
  • parent
  • [–] 2 points 10 months ago

    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.

  • source
  • [+] -15 points 10 months ago (2 children)

    dd if=/dev/zero of=/var

    But really, remove what you don't use and/or stop using flatpak.

  • source
  • hideshow 4 child comments
  • [–] 17 points 10 months ago (1 child)

    FYI Don’t use this command. I think it was intended as a joke, but I just want to clarify.

  • source
  • parent
  • hideshow 2 child comments
  • [+] -6 points 10 months ago (1 child)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 7 points 10 months ago (1 child)

    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.

  • source
  • parent
  • hideshow 2 child comments