Root filesystem /dev/sda1 · 193 GB total · analysed & pruned on 3 October 2026.
Freed space jumped from 12 GB → 69 GB — a 5.7× increase in headroom.
| Source | What it was | Freed | Status |
|---|---|---|---|
| Docker container logs | photon-electrs was spamming one 28 GB log file | ≈ 28 GB | truncated |
| Gradle build cache | ~/.gradle/caches — regenerates on next build | ≈ 10 GB | cleared |
| Dev download caches | pip, Playwright, Puppeteer, pnpm, uv, dfinity | ≈ 6.7 GB | cleared |
| System logs | syslog (2.7 GB) + rotated logs + journal + app logs | ≈ 8 GB | pruned |
| npm cache | ~/.npm/_cacache — regenerates | ≈ 4.2 GB | cleared |
| apt cache | /var/cache/apt downloaded .deb packages | ≈ 0.1 GB | cleaned |
All of the above is either pure waste (log spam) or regenerable cache — nothing was deleted from databases, volumes, or application data.
/home/waheed | Project repos & toolchains (PhotonBolt, HRSanad, Baqala, MBBS…) | 63 GB |
/var/lib/docker | Images (14 GB overlay) + volumes (7 GB: Postgres, Redis, Supabase) | 26 GB |
/usr | System binaries & libraries | 5.2 GB |
/var/snap | Snap package data | 11 GB |
/etc/docker/daemon.json:
{ "log-driver":"json-file", "log-opts":{ "max-size":"50m", "max-file":"3" } } then restart Docker (applies to new containers), or set --log-opt max-size per container.docker image prune (dangling, ≈ 5 GB) and docker builder prune (≈ 2.4 GB). Volumes were left untouched to protect your databases.photon-electrs verbosity — the electrs index was logging heavily; lowering its log level prevents regrowth.~/.rustup (1.9 GB toolchains) and Docker volumes — removing these would break builds / lose data.Re-run the analysis anytime: sudo du -xhd1 / | sort -h | tail and df -h /.
/var/snap? (11 GB here)
Snap apps are installed in three separate places. /var/snap is where each installed snap keeps
its writable data — databases, configuration and user content — stored outside the read-only app package
so it survives updates. Think of it as each snap's private “data folder / home”.
| Location | What lives there | Read/write | Size |
|---|---|---|---|
/snap | The app images themselves (mounted, compressed squashfs) | read-only | ~mounts |
/var/lib/snapd | The downloaded .snap files + snapd's own state | system | 3.4 GB |
/var/snap | Per-snap writable DATA — this is the 11 GB | read-write | 11 GB |
Inside /var/snap, almost all of it is one app — your self-hosted Nextcloud server:
common/nextcloud | Actual user files — uploads, documents, photos (shared across versions) | 7.6 GB |
54257/ (current rev) | App code + config + bundled MySQL database for this version | 1.5 GB |
54178/ (old rev) | Previous version, kept by snapd for rollback | 1.5 GB |
| other snaps | oracle-cloud-agent, cups, chromium, cores… (tiny data) | ~19 MB |
54178) is kept only for rollback. Snapd keeps 2 by default; it clears on the next successful refresh, or you can cap it: snap set system refresh.retain=2.occ trashbin:cleanup) can free more without losing live files.In short: /var/snap = snap apps' data. Here it's your Nextcloud cloud storage — mostly genuine files you want to keep, with only ~1.5 GB of old-revision overhead that's safely reclaimable.