From: Anthony Roberts <btrfs-devel@arbitraryconstant.com>
To: Linux btrfs <linux-btrfs@vger.kernel.org>
Subject: questions about GRUB and BTRFS
Date: Tue, 24 Feb 2009 18:32:45 -0700 [thread overview]
Message-ID: <a3a222ba714187fedfe43fe9f7086242@smtp.arbitraryconstant.com> (raw)
Hi,
A quick googling turns up posts that GRUB support for BTRFS is planned. My
curiosity is more towards how this will be managed, because the way this is
currently implemented with software RAID/LVM is quite haphazard. I
therefore have some questions about GRUB + BTRFS:
-With GRUB booting, it's easy to think of awkward use cases and limitations
unless it's capable of discovering BTRFS instances, and can boot by
specifying BTRFS UUID + subvolume. That seems quite ambitious, but is this
planned "eventually"?
-Might it be possible to tweak the userspace component of GRUB to install
the bootloader to every member device? This seems necessary for reliable
booting and rebuilding after a dead disk.
-64 kb at the beginning of the device is plenty for MBR + GRUB stage 1 +
1.5. Might this allow bootable BTRFS without paritions being used at all?
The space used for partitioning is negligible, however we're on the cusp of
disks that are too big to partition with MBR, and GPT booting doesn't seem
well supported yet.
There's obviously no point in getting worked up about this before
production ready support is available in the first place. :) However, I am
curious about what sort of implementation is planned.
-Anthony
next reply other threads:[~2009-02-25 1:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 1:32 Anthony Roberts [this message]
2009-02-25 1:53 ` questions about GRUB and BTRFS Dmitri Nikulin
2009-02-25 6:03 ` Lee Trager
2009-02-25 18:19 ` Thomas Kuther
2009-02-25 18:22 ` Chris Mason
2009-02-25 20:04 ` Anthony Roberts
2009-02-25 20:22 ` Chris Mason
2009-04-21 15:13 ` David Woodhouse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a3a222ba714187fedfe43fe9f7086242@smtp.arbitraryconstant.com \
--to=btrfs-devel@arbitraryconstant.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox