Recovering from Failed Updates with openSUSE Snapper and Btrfs
Learn how openSUSE leverages Btrfs and Snapper to provide atomic system rollbacks, allowing you to undo failed updates directly from the boot menu without losing user data.
Loading…
ReadMeFeed / Community knowledge
#snapper
Real questions. Useful conversations. Find the people who know your stack.
opensuseTumbleweed's Safety Net: Automatic Btrfs Snapshots Before Every Update
openSUSE Tumbleweed pairs continuous zypper dup updates with automatic Btrfs Snapper snapshots, letting you revert the whole system state instead of chasing package downgrades.
Managing System Recovery in openSUSE Leap: Btrfs Snapshots vs. Manual Backups
Learn how to use openSUSE Leap's Btrfs and Snapper integration to perform atomic system rollbacks, manage disk space, and recover from failed updates.
Could not mount Btrfs subvolume '/@/snapshots'
Deployment Failure with Snapper Error The deployment process halts when encountering the specific error string 'Could not mount Btrfs subvolume '/@/snapshots' on openSUSE. Snapper Snapshot Handling This failure points directly to the snapper component's inability to manage Btrfs subvolume snapshots during the installation phase. Given the version dependency
Snapper post‑upgrade snapshot retention after manual rollback in openSUSE Leap
When a zypper dup upgrade fails on openSUSE Leap, Snapper creates a pre‑upgrade snapshot that can be rolled back and leaves the failed post‑upgrade snapshot intact for inspection. The release notes note an unresolved decision about whether this failed post‑upgrade snapshot should be automatically removed after a successful manual rollback, leaving the action
Snapper snapshot missing after zypper transaction
The goal is to determine whether openSUSE Snapper creates a read-only Btrfs snapshot immediately after a zypper package transaction completes, or only when the systemd timer expires. The documentation does not explicitly define whether snapshot creation is tied to transaction completion or timer expiry. Testing without production credentials is also uncertai
Btrfs snapshot retention configuration on OpenSUSE minimal-install servers
Problem Statement OpenSUSE's default installation enables Btrfs snapshot auto-creation via snapper for system and user data. On low-traffic servers with minimal workloads, this feature can lead to unbounded disk usage if retention policies are not explicitly configured. The trade-off between convenience and storage cost becomes critical when running cost-sen
Snapper snapshot retention limits and disk space exhaustion
Btrfs Snapshot Management openSUSE utilizes the Snapper framework to automate Btrfs snapshots during Zypper package operations. The system relies on a configuration file to define retention limits for hourly, daily, weekly and monthly snapshots to prevent the root partition from reaching full capacity. While these limits manage snapshot count, actual disk sp
Snapper space-aware cleanup on openSUSE: enable qgroups or keep quotas off?
openSUSE Leap and Tumbleweed ship a Btrfs root with Snapper preconfigured: package transactions create pre/post snapshot pairs, and the shipped root config leaves timeline snapshots disabled, pruning mainly by number and empty-pre-post rules. These defaults have shifted across releases, so they should be read from the installed system rather than assumed. Th