[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

you are viewing a single comment's thread
view the rest of the comments
[–] 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