linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gene Czarcinski <gene@czarc.net>
To: "linux-btrfs@vger.kernel.org list" <linux-btrfs@vger.kernel.org>
Subject: Re: /boot as a btrfs subvolume
Date: Sun, 06 Jan 2013 09:37:20 -0500	[thread overview]
Message-ID: <50E98C20.3040504@czarc.net> (raw)
In-Reply-To: <C4D7AC34-9841-4E58-BE5D-FF30C85FBD34@colorremedies.com>

On 01/05/2013 04:32 PM, Chris Murphy wrote:
> On Jan 5, 2013, at 2:17 PM, Gene Czarcinski <gene@czarc.net> wrote:
>
>> As of the latest updates to anaconda and grub2 for Fedora 18, it is now possible to install with /boot as a btrfs subvolume.  The way that grub2 is handling this is the "reach down" to the files it needs as if the subvolume was a directory.
> Also for what it's worth, it also works for multiple device Btrfs volumes, all profiles supported by GRUB2. For me GRUB fails to navigate Btrfs for RAID0 if there are 5+ devices. Single still works, oddly RAID10 still works. So some regression is needed to figure out what's going on there. May be a bug, but honestly it's still pretty cool.
>
> Also to test is if installing grub to each device, in a multiple device raid1 or raid10 volume, still allows it to be bootable with any one device removed from the volume. I think it'll work.
>
There is also issues with btrfs and os-prober for multiboot ... it does 
not currently work.  I hacked up a patch to get it to work but have 
since had second thoughts about how multiboot should be handled.  I now 
prefer a separate grub partition, os-prober disabled, and a grub.cfg 
file which points to the grub.cfg for each individual system.

BTW, although you can install and boot boot installed in a logical 
volume, that system is not supported in os-prober multiboot.

Gene

      reply	other threads:[~2013-01-06 14:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-05 21:17 /boot as a btrfs subvolume Gene Czarcinski
2013-01-05 21:27 ` Chris Murphy
2013-01-06 14:44   ` Gene Czarcinski
2013-01-06 19:11     ` Chris Murphy
2013-01-06 19:17       ` Swâmi Petaramesh
2013-01-06 20:05         ` Gene Czarcinski
2013-01-07  2:00           ` Chris Murphy
2013-01-07 15:42             ` Gene Czarcinski
2013-01-07 18:42               ` Chris Murphy
2013-01-07 21:41                 ` Gene Czarcinski
2013-01-07 22:04                   ` Chris Murphy
2013-01-07 17:48           ` Swâmi Petaramesh
2013-01-07 19:28             ` Chris Murphy
2013-01-05 21:32 ` Chris Murphy
2013-01-06 14:37   ` Gene Czarcinski [this message]

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=50E98C20.3040504@czarc.net \
    --to=gene@czarc.net \
    --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;
as well as URLs for NNTP newsgroup(s).