From 01fcff45c1e8b127349841c33deed29bdb16961a Mon Sep 17 00:00:00 2001 From: Padreug Date: Tue, 26 May 2026 11:52:49 +0200 Subject: [PATCH] =?UTF-8?q?chore(nix):=20tighten=20ATM=20GC=20=E2=80=94=20?= =?UTF-8?q?daily=20at=2003:30,=20persistent?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Was: weekly, no persistence. Problem: 15GB eMMC + ~7GB closure means cross-release upgrades are always tight. Weekly cadence stacked up to a week of generations under the 04:00 auto-upgrade. Persistent=false also meant a Sintra powered off at 03:30 skipped GC until next week. Now runs daily at 03:30, 30 min before the 04:00 nixos-upgrade so each upgrade attempt gets the freshest headroom. 7d retention unchanged. This is a periodic-cleanup fix only — cross-release in-place upgrades on 15GB eMMC will still hit the disk-full wall (caught 2026-05-26 on 24.05 → 24.11). Reflash remains the answer there. Co-Authored-By: Claude Opus 4.7 (1M context) --- deploy/nixos/configuration.nix | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/deploy/nixos/configuration.nix b/deploy/nixos/configuration.nix index 9ea2f21..d473a42 100644 --- a/deploy/nixos/configuration.nix +++ b/deploy/nixos/configuration.nix @@ -199,11 +199,18 @@ auto-optimise-store = true; }; - # Garbage collection + # Garbage collection — daily at 03:30, 30 min before the 04:00 auto- + # upgrade so each upgrade attempt gets the freshest headroom. 15GB + # eMMC + ~7GB closure means cross-release upgrades are always tight; + # weekly was leaving up to a week of generations stacked when the + # upgrade ran (caught 2026-05-26 on the 24.05 → 24.11 attempt). + # persistent so a Sintra that was powered off at 03:30 still runs the + # GC on next boot rather than skipping until next week. gc = { automatic = true; - dates = "weekly"; + dates = "03:30"; options = "--delete-older-than 7d"; + persistent = true; }; }; }