https://fedoraproject.org/wiki/Changes/BtrfsByDefault Summary: - Create additional subvolumes to exclude locations from a snapshotting send and receive regime. This is an optimization. - Desired but not a requirement of the change proposal. Detail: Creating snapshots on btrfs is not recursive, the snapshot stops at nested subvolumes. Options: - Create subvolumes in nested form to prevent certain locations from being snapshot - Dilemma: A rollback will need to move these subvolumes to a new location, because they're nested in the old/abandoned subvolume. - Create subvolumes at the top-level to prevent certain locations from being snapshot and add them to fstab or native systemd mount. - Dilemma: results in 'invalid cross-device link' when reflinking; mv will fallback to an oldbig copy. Locations: /var/log/ /var/lib/libvirt/images/ /var/lib/containers/ Scope: Anaconda knows how to do this already, just change the kickstart to add additional subvolumes. Possible additional locations as part of a larger strategy for user home snapshotting/restore and backup integration: ~/.local/share/gnome-boxes/images/ ~/.cache ~/.local/share/Trash/
Consolidating btrfs issues for design and planning logics. This issue is now found here: #8 create additional subvolumes at install time https://pagure.io/fedora-btrfs/project/issue/8