aiolabs/bitspire
9
0
Fork 0
Code Issues 52 Pull requests 2 Projects Releases Packages Wiki Activity Actions

chore(nix): tighten ATM GC — daily at 03:30, persistent

Browse source 
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) <noreply@anthropic.com>
This commit is contained in:
Padreug 2026-05-26 11:52:49 +02:00
commit 01fcff45c1
1 changed files with 9 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

11
deploy/nixos/configuration.nix
View file

@ -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;
};
};
}