I believe the primary use case would be when you wish to target the volume (i.e. grub-install /dev/sda1).
If the concern is size, this has been officially resolved with Boot Area B's specifications. https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg34016.html We do leave the first 1MB of each device alone. Can we do 256K-1024K for the boot loader? We don't have an immediate need for the extra space, but I'd like to reserve a little more than the extra 64KB. With a small loader in Boot Area A and the primary payload in Boot Area B, this should alleviate most size constraints. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/759772 Title: grub2: btrfs: does not install core.img to boot block To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/759772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
