OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
apps-services high common DISPUTE

Reclaim a full root filesystem from journal logs and the pacman cache

archomarchyendeavouroscachyosmanjarosystemdpacmandesktoplaptop
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

The generic Arch advice is sound and the three cited wiki pages all support it, but the record is mis-specialised to Omarchy 4 in four places and its first diagnostic command is actively wrong on the stock Omarchy layout. Confirmed on this machine (omarchy 4.0.2-1, systemd 261.2-1, pacman-contrib 1.13.1-1, kernel 7.1.9): the installer puts /var/log on the @log subvolume and /var/cache/pacman/pkg on @pkg, and btrfs gives each subvolume its own device number, so du -xh --max-depth=1 /var skips both of the directories this record is about. Measured here it reported /var/cache as 8.6M and omitted /var/log entirely, while the same command without -x reported /var/cache 6.8G and /var/log 682M. The four-subvolume layout is not local drift: research/tools/make-test-vm.sh, written to match the ISO configurator's own output, declares @, @home, @log and @pkg. Those subvolumes share the root filesystem's free pool rather than holding a quota, confirmed because df -h prints an identical 475G size and 191G available for /, /var/log and /var/cache/pacman/pkg, so the record's mechanism claim that filling either fills / is correct and was kept. Second defect, in the cause: the pacman cache does not grow without bound on Omarchy 4, because /usr/bin/omarchy-update calls omarchy-update-pkg-prune, which is sudo paccache -rk2, on every update, and that script is byte-identical at upstream tag v4.0.3 published 2026-09-08. Third, the symptom: on Omarchy 4 the user does not reach libalpm's message, verified as the format string "Partition %s too full: %jd blocks needed, %ju blocks free" in /usr/lib/libalpm.so, because omarchy-update-requires-free-space aborts first with "You need at least 10 GiB free to safely update Omarchy." Fourth, the verify step's pacman -Syu cannot run at all: /usr/share/libalpm/hooks/00-omarchy-update-guard.hook fires AbortOnFail into omarchy-update-pacman-guard, and reading that script shows it aborts whenever both S and u are present, so pacman -S pacman-contrib in the fix is safe but the verify command is not. The previous auditor noted that guard as a nit and nobody changed the record body. Two smaller points folded in: pacman-contrib reports Required By : omarchy here, so the install line is a no-op on Omarchy, and omarchy-update already offers the orphan step through omarchy-update-orphan-pkgs, which runs the same pacman -Qtdq then pacman -Rns. What I kept because it held: rotate before vacuum (Arch Systemd/Journal line 175), the journald.conf.d drop-in with SystemMaxUse=, paccache -r keeping three and paccache -ruk0 (Arch Pacman lines 269 and 283), and paccache.timer really shipping in pacman-contrib (pacman -Ql pacman-contrib lists /usr/lib/systemd/system/paccache.timer). Enabling that timer is not noise: systemctl is-enabled paccache.timer reports disabled on this stock Omarchy install, /etc/conf.d/pacman-contrib has an empty PACCACHE_ARGS so the unit runs a bare paccache -r, and Omarchy ships no journald drop-in at all, since /etc/systemd/journald.conf.d does not exist and systemd-analyze cat-config systemd/journald.conf shows only the package-stock file with #SystemMaxUse= commented out. I added a snapper pointer because /etc/snapper/configs/root here has SUBVOLUME="/" with NUMBER_LIMIT="5" and TIMELINE_CREATE="no", matching upstream default/snapper/root, so omarchy update leaves up to five snapshots of / and a reader who trims the journal and cache and still sees / full has nowhere else to look. Frequency dropped from very-common to common with a reason: the single largest driver the cause names, an unbounded package cache, is pruned on every update on this platform and the 10 GiB pre-check catches the rest early. Severity left at high, since a full root still stops updates. Not exercised: I have no sudo, so I ran no vacuum, no paccache and no orphan removal, did not fill a disk to see either error text emitted, and could not run btrfs subvolume list / or snapper -c root list, both of which refused with Operation not permitted. Upstream's own comment at bin/omarchy-update line 29 says the cache sits on the snapshotted subvolume, which disagrees with the @pkg subvolume I measured here, and I did not take a snapshot to settle it, so the corrected text asserts nothing either way about snapshot interaction with the cache. All three cited URLs resolved and support what the record draws from them, so nothing was removed.

The cause above was rewritten on 2026-09-11 to match this note; the fix was corrected by the audit itself.
RISK

paccache -rk0 (keeping zero versions) removes your ability to downgrade a package offline after a bad update, so keep at least one. On Omarchy 4 keep at least two: omarchy-update-pkg-prune runs paccache -rk2 and calls the cache the only offline downgrade path, so trimming below that weakens Omarchy's own rollback story.

pacman -Qtdq | pacman -Rns - removes anything no longer required by an explicitly installed package. Read the list before confirming, since it can pull out things you actually use if they were originally installed as dependencies.

Do not delete /var/log/journal itself to reclaim space. Rotate and vacuum instead, because removing that directory turns persistent logging off and you lose the logs from the next crash.

Symptom

On plain Arch, pacman -Syu fails with error: Partition /var/cache/pacman/pkg too full: <n> blocks needed, <n> blocks free or not enough free disk space, and df -h shows / at 100%.

On Omarchy 4, omarchy update refuses before it starts anything:


You need at least 10 GiB free to safely update Omarchy.

Either way I have not knowingly installed anything huge.

Cause

Two directories grow on Arch by default. /var/cache/pacman/pkg/ keeps every downloaded package version, and /var/log/journal/ grows to 10% of the filesystem with a soft cap at 4 GiB, because SystemMaxUse= is unset in the stock journald.conf.

On Omarchy 4 the cache half is already handled and the journal half is not. Every omarchy update runs omarchy-update-pkg-prune, which is sudo paccache -rk2, so the cache is trimmed to two versions per package on each update. Omarchy ships no journald drop-in, so the 4 GiB soft cap is what applies to the journal.

Omarchy's installer also puts /var/log on the @log btrfs subvolume and /var/cache/pacman/pkg on @pkg. Those share the root filesystem's free space rather than holding a quota of their own, so filling either one still fills /. A third consumer that plain Arch does not have is the snapper snapshots of /, up to five of them, taken by omarchy update.

Fix

Find out where it went. Do not pass -x to du here: Omarchy puts /var/log and /var/cache/pacman/pkg on separate btrfs subvolumes, which carry their own device numbers, so -x silently skips both of the directories you are looking for.


sudo du -h --max-depth=1 /var | sort -h | tail
journalctl --disk-usage
du -sh /var/cache/pacman/pkg
findmnt -t btrfs

Trim the journal. Files must be rotated before vacuum can touch them:


sudo journalctl --rotate
sudo journalctl --vacuum-size=200M

Cap it permanently with a drop-in. Omarchy 4 ships no journald drop-in of its own, so this directory does not exist yet:


sudo mkdir -p /etc/systemd/journald.conf.d
sudo tee /etc/systemd/journald.conf.d/00-journal-size.conf >/dev/null <<'EOF'
[Journal]
SystemMaxUse=200M
EOF
sudo systemctl restart systemd-journald.service

Trim the pacman cache. paccache -r keeps the 3 most recent versions of each package:


sudo paccache -r
sudo paccache -ruk0          # drop ALL cached versions of uninstalled packages

On plain Arch, install pacman-contrib first, then enable the weekly timer:


sudo pacman -S pacman-contrib
sudo systemctl enable --now paccache.timer

On Omarchy 4, pacman-contrib is already a dependency of omarchy, so that install is a no-op. paccache.timer ships disabled and omarchy update prunes the cache itself, so the timer is only worth enabling if you go long stretches between updates.

Remove orphans. omarchy update already offers this step through omarchy-update-orphan-pkgs, so on Omarchy 4 you rarely need it by hand:


pacman -Qtdq | sudo pacman -Rns -

If / is still full on Omarchy 4 after all of that, look at the snapshots omarchy update leaves behind:


sudo snapper -c root list

Verify

df -h / shows free space again and journalctl --disk-usage is under your cap.

On Omarchy 4, omarchy update gets past its free-space check and completes. Do not test with pacman -Syu: /usr/share/libalpm/hooks/00-omarchy-update-guard.hook aborts it whatever the disk looks like. On plain Arch, pacman -Syu completes.

Where you enabled the timer, systemctl is-enabled paccache.timer reports enabled.

Sources

disk-full-journal-and-pacman-cache