Тема: btrfs
-
Checking and repairing filesystems: fsck, xfs_repair and btrfs check on an unmounted filesystem
ext4, XFS and Btrfs each ship their own checker with different safety rules: e2fsck and xfs_repair must run on an unmounted filesystem (xfs_repair has a -n dry-run mode), while btrfs check defaults to read-only and warns strongly against --repair. Exit codes and dry-run output, not intuition, decide whether a repair is needed.
-
Btrfs snapshots and rollback with snapper on SUSE: pre/post pairs, GRUB boot, and cleanup
On a Btrfs root, SUSE's snapper takes a pre/post snapshot pair around every zypper or YaST change, lists them with snapper list, and can either roll the whole system back or boot directly into an old snapshot from the GRUB menu. Old snapshots are cleaned up automatically, but the cleanup policy — not disk size alone — decides how much history is kept.
-
Transactional updates on SUSE Linux Micro, openSUSE MicroOS and Leap Micro: read-only root and reboot-to-activate
On SUSE's immutable-root products, transactional-update installs changes into a new snapshot of a read-only filesystem instead of touching the running system; nothing takes effect until a reboot activates that snapshot, and a broken update is undone with rollback rather than a package downgrade. On regular SLES the same mechanism exists but is documented as a technology preview for a read-only root, not the default.
Машиночитаемо: JSON