Using openSUSE Btrfs Snapshots with Snapper for Safe System Updates
Learn how openSUSE automatically creates Btrfs snapshots before every zypper transaction, how to list and roll back those snapshots, and what storage considerations to watch.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how openSUSE automatically creates Btrfs snapshots before every zypper transaction, how to list and roll back those snapshots, and what storage considerations to watch.
Snapper's pre/post snapshots make a bad openSUSE update reversible — but only for the root subvolume. How undochange and rollback differ, and what they leave behind.
A step‑by‑step diagnostic guide for using openSUSE Snapper with Btrfs to identify and roll back unwanted system changes after updates or configuration errors, including ordered checks, targeted fixes, and escalation paths.
Fedora’s switch to Btrfs as the default filesystem gives instant snapshots, compression, and subvolume isolation—great for recovery, but it can fragment write‑heavy workloads and mislead disk usage reports. Learn how to test, use, and mitigate Btrfs in Fedora.
Explore how Fedora Workstation uses Btrfs subvolumes to eliminate rigid partitioning and enable flexible disk management and snapshots.
Learn how to use Snapper and Btrfs snapshots in openSUSE to recover from failed updates and system instability using read-only boots and atomic rollbacks.
Learn how openSUSE’s default Btrfs layout combined with Snapper provides instant, space‑efficient system snapshots and one‑command rollbacks after updates or package changes.
A concise decision guide that compares Btrfs, ext4 and XFS for the openSUSE Leap root partition, covering snapshot support, performance, encryption compatibility and validation steps.
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.