On Fri, Oct 25, 2019 at 11:47 AM Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > > I see references to root and chunk trees, but not the log tree. > > If boot related files: kernel, initramfs, bootloader configuration > files, are stored on Btrfs; and if they are changed in such a way as > to rely on the log tree; and then there's a crash; what's the worse > case scenario effect? > > At first glance, if the bootloader doesn't support log tree, it would > have a stale view of the file system. Since log tree writes means a > full file system update hasn't happened, the old file system state > hasn't been dereferenced, so even in an SSD + discard case, the system > should still be bootable. And at that point Btrfs kernel code does log > replay, and catches the system up, and the next update will boot the > new state. > > Correct? Pretty sure this is the current and self-contained Btrfs code for GRUB http://git.savannah.gnu.org/cgit/grub.git/tree/grub-core/fs/btrfs.c -- Chris Murphy
