OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
omarchy-core critical occasional DISPUTE

Keep your snapshot history when the Quattro upgrade replaces the Snapper config

omarchyomarchy-3omarchy-4quattro-upgradesnapperbtrfs
CORRECTED An auditor found the fix wrong or incomplete and rewrote it. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

Confirmed on 4.0.4-1 and quattro: install/config/snapper.sh is identical in both. It installs the template over /etc/snapper/configs/root, writes SNAPPER_CONFIGS="root" to /etc/conf.d/snapper, and ends with systemctl enable --now snapper-cleanup.timer. The template sets NUMBER_MIN_AGE=0, NUMBER_LIMIT=5, NUMBER_LIMIT_IMPORTANT=5 and TIMELINE_CREATE=no. The timer is OnBootSec=10m and OnUnitActiveSec=1h. bin/omarchy-upgrade-to-quattro calls create_pre_upgrade_snapshot (omarchy-snapshot create, which uses -c number) and then configure_snapper_policy. snapper(8) documents modify -c and set-config. The fix holds. #12551 is open and PR #9633 for the conf.d overwrite is unmerged. Two corrections. First, #12551 says the pre-upgrade snapshot was pushed past the limit by snap-pac's pre/post pairs, and snap-pac is not an Omarchy default. Without it the pre-upgrade snapshot can survive, so the symptom now carries that condition. Snapshots made with plain snapper create without -c also survive. Second, the danger now notes that MAX_SNAPSHOT_ENTRIES=6 in /etc/limine-entry-tool.d/omarchy-defaults.conf caps the Limine menu whatever NUMBER_LIMIT is, and that snapshots without a cleanup algorithm accumulate. Not exercised: no snapper command was run.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.
RISK

Raising NUMBER_LIMIT keeps more snapshots and uses more disk space. omarchy update refuses to start with under 10 GiB free, so choose limits your root filesystem can hold. Snapshots created without a cleanup algorithm are never removed automatically and accumulate until you delete them. The Limine menu still lists at most 6 snapshots (MAX_SNAPSHOT_ENTRIES=6 in /etc/limine-entry-tool.d/omarchy-defaults.conf), so to boot more of them set a higher MAX_SNAPSHOT_ENTRIES in /etc/default/limine.

Symptom

A few minutes after upgrading from Omarchy 3 to 4 with omarchy-upgrade-to-quattro, most btrfs snapshots are gone and only the newest 5 numbered snapshots remain. That includes ones you took by hand with omarchy-snapshot create or snapper create -c number. If the upgrade's package transactions created extra numbered snapshots (for example with snap-pac installed, which Omarchy does not ship), the pre-upgrade snapshot the upgrade itself took is deleted too. Right after the upgrade everything was still listed. /etc/snapper/configs/root is now byte-identical to /usr/share/omarchy/default/snapper/root, and /home snapshots stopped being made.

Cause

configure_snapper_policy() in the Quattro upgrade runs install/config/snapper.sh, which does install -m 0644 "$template" /etc/snapper/configs/root with no merge, no backup and no message beyond Configuring Omarchy Snapper snapshot retention. The template, /usr/share/omarchy/default/snapper/root (checked on 4.0.4-1), sets NUMBER_LIMIT="5", NUMBER_LIMIT_IMPORTANT="5", NUMBER_MIN_AGE="0" and TIMELINE_CREATE="no". With a minimum age of 0 the next snapper-cleanup.timer run (OnBootSec=10m, then hourly) can delete any number-cleanup snapshot beyond the newest 5, however young. The same script also rewrites /etc/conf.d/snapper to SNAPPER_CONFIGS="root", de-registering a home config. btrfs snapshot deletion is irreversible.

Fix

Stopping snapper-cleanup.timer beforehand does not help: the upgrade's own install/config/snapper.sh ends with systemctl enable --now snapper-cleanup.timer. Protect snapshots in a way the upgrade cannot undo. Snapper's cleanup only deletes snapshots that carry a cleanup algorithm, so a snapshot made without -c survives any NUMBER_LIMIT.

Before running the Quattro upgrade, save your policy and take a rollback snapshot that cleanup will never touch:


sudo cp -a /etc/snapper/configs/root /etc/snapper/configs/root.pre-quattro
sudo cp -a /etc/conf.d/snapper /etc/conf.d/snapper.pre-quattro
sudo snapper -c root create -d "before quattro upgrade"
sudo snapper -c root list    # the new snapshot shows an empty Cleanup column

For existing snapshots you want to keep, clear their cleanup algorithm the same way, using the numbers from snapper list, and check the Cleanup column is empty afterwards:


sudo snapper -c root modify -c "" 42

Right after the upgrade finishes, put back the values you want with snapper itself:


diff /etc/snapper/configs/root.pre-quattro /etc/snapper/configs/root
sudo snapper -c root set-config NUMBER_MIN_AGE=1800 NUMBER_LIMIT=10 NUMBER_LIMIT_IMPORTANT=10
sudo snapper -c root get-config | grep -E 'NUMBER_|TIMELINE'

If you had a home config, restore its registration with sudo cp /etc/conf.d/snapper.pre-quattro /etc/conf.d/snapper and check sudo snapper -c home list.

If the upgrade already ran, do the set-config step immediately to protect what is left. Snapshots already deleted cannot be recovered. Snapshots made without a cleanup algorithm are never removed automatically, so delete them yourself with sudo snapper -c root delete <number> once you no longer need them.

Verify

sudo snapper -c root get-config shows your NUMBER_MIN_AGE and NUMBER_LIMIT, and snapper -c root list still shows the pre-upgrade snapshot an hour after the upgrade (after at least one snapper-cleanup.service run in journalctl -u snapper-cleanup).

Sources

quattro-upgrade-replaces-snapper-config-deletes-snapshots