From ca197d2ce7d524f64fd2aee79b71eb0145e5d28d Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Wed, 8 Jul 2026 08:02:07 -0500 Subject: fix(maint): raise pacman cache warn threshold to 20GB The 10GB threshold sat below the keep-3 steady state on both hosts (ratio 12.6GB, velox 10.8GB after pruning), so the warning persisted with nothing left to clean. paccache keeps three versions per package and never expires by age, which puts the honest ceiling near 17-19GB. At 20GB the metric stays quiet in steady state but still fires within about two months if the paccache timer dies. I installed it on both hosts and the warning cleared on each. --- configs/maintenance-thresholds.toml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'configs/maintenance-thresholds.toml') diff --git a/configs/maintenance-thresholds.toml b/configs/maintenance-thresholds.toml index 161b4c2..d2c85e8 100644 --- a/configs/maintenance-thresholds.toml +++ b/configs/maintenance-thresholds.toml @@ -43,7 +43,8 @@ zfs_count_warn = 1000 # runaway retention zfs_space_warn_pct = 20 # snapshot space vs pool capacity [packages] -cache_warn_gb = 10 # suggest paccache beyond the weekly keep-3 +cache_warn_gb = 20 # above keep-3 saturation (~17-19GB on ratio); + # fires within ~2 months if the paccache timer dies keyring_warn_days = 60 # stale archlinux-keyring silently breaks updates [security] -- cgit v1.2.3