https://bugzilla.redhat.com/show_bug.cgi?id=1576413 --- Comment #9 from Marian Csontos <mcsontos@xxxxxxxxxx> --- I think snpshots of /boot has its own set of problems. One of snapper's flaws when using BTRFS is exactly that - it keeps information about snapshots inside the filesystem which is "snapshotted". I wonder, if you have multiple snapshots of /boot, where do you keep information about those snapshots and grub.cfg to pick the snapshot+kernel+initrd+cmdline to boot? And if you boot into a snapshot, and want to make an update to that config, where to save that information? Either you still keep data inside "master" snapshot of /boot, or you need to keep it up to date somehow, don't you? Or do you move the problem to EFI boot partition or elsewhere? And than one can not "snapshot" that, and files are saved/installed there too. And should the FS get dirty, how does one fsck it? Of course /boot can get dirty itself too, but it is rather low traffic, compared to /. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx
