Gregory's Server@akhil
> This setup will make all snapshots created by Snapper be stored outside of the @ subvolume. This allows replacing @ without losing the snapshots.
I have seen this multiple times already, but as with all other subvolumes, they are automounted when the parent subvolume is mounted and aren't included in snapshots, just like @/var/cache
So @/.snapshots and @ snapshots works just the same (except @/.snapshots gets automounted).
Correct me if I'm wrong.
@tippfehlr
You place any number of subvolumes in to main subvolume (subvolid=5), the same place where @ and @snapshots are placesd, and then add all you subvolumes into fstab using subvol mount option. So the root subvolume does not contain any nested subvolumes, caches, logs and whatever you would not want to keep in your snapshots.
You may try to install #Garuda or #EndeavourOS and #OpenSUSE in VM with btrfs root and see how partitioning is done there.
Also I prefer snapper's / OpenSUSE way to mount root subvolume from mutable snapshot but in Arch this requires some hacks to get it done.
@tippfehlr
You place any number of subvolumes in to main subvolume (subvolid=5), the same place where @ and @snapshots are placesd, and then add all you subvolumes into fstab using subvol mount option. So the root subvolume does not contain any nested subvolumes, caches, logs and whatever you would not want to keep in your snapshots.