ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Fedora Workstation uses Btrfs with zstd compression and separate subvolumes for / and /home. Learn how to verify compression, manage snapshots, disable CoW for VMs, and avoid common pitfalls like treating snapshots as backups.
Diagnostic guide for Timeshift snapshot failures on Linux Mint 21.x/22.x Cinnamon: recognize the failure mode, run five ordered checks, apply targeted fixes for BTRFS/RSYNC modes, and verify the full create, list, GRUB, and restore cycle.
openSUSE's transactional-update applies system changes atomically inside a new Btrfs snapshot, activated only at reboot. Rollback is a boot-menu choice — but /var, /home, and /etc live outside the snapshot boundary.
Learn how to configure Snapper on OpenSUSE to create, prune, and roll back Btrfs snapshots around zypper transactions. A practical guide with example config, commands, and trade‑offs to keep your root filesystem safe and tidy.
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.
Arch Linux users utilizing Btrfs subvolumes often rely on snapshots to revert the system state after a failed update. While tools like Timeshift can restore the root subvolume to a previous state, the synchronization between the filesystem state and the Pacman package database requires careful consideration. The primary constraint is that the Pacman database
fedora
opensuse
archlinux