public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Anthony Roberts <btrfs-devel@arbitraryconstant.com>
Cc: Linux btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: questions about GRUB and BTRFS
Date: Wed, 25 Feb 2009 15:22:23 -0500	[thread overview]
Message-ID: <1235593343.32346.73.camel@think.oraclecorp.com> (raw)
In-Reply-To: <6e246ee64cdb6decfd7153436888efcb@smtp.arbitraryconstant.com>

On Wed, 2009-02-25 at 13:04 -0700, Anthony Roberts wrote:
> Hi Chris,
> 
> Cheers for the informative response. :)
> 
> > In the ideal implementation, the grub.conf has a list of devices it is
> > allowed to scan, and we put the FS uuid directly in there, let grub scan
> > them and we'll be able to boot off multiple volumes in that way.
> 
> Hm... perhaps it doesn't even need that much. It we're specifying devices,
> might it simply pull the UUID out of the initial device it's given, kinda
> like how the current mounting process works? Enumeration of the drives
> changes as they come and go, but it doesn't really matter what "hd0" is
> today as long as it's a member device.

The problem is that grub would need some way of knowing which devices to
scan.  I'd hate to see it off running through everything in a san.

> 
> This suggests another question for me... right now you can specify a root=
> command line to the kernel, though there's other stuff like nfsroot= where
> more parameters are needed. Is it possible to add a btrfsroot= option with
> a UUID+subvolume?

I'm not a huge fan of initrds, but the distro initrd scripts already
have this kind of goodness hooked in.  I think that's the best place for
it.

-chris



  reply	other threads:[~2009-02-25 20:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-25  1:32 questions about GRUB and BTRFS Anthony Roberts
2009-02-25  1:53 ` 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 [this message]
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=1235593343.32346.73.camel@think.oraclecorp.com \
    --to=chris.mason@oracle.com \
    --cc=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