grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Michael Chang <mchang@suse.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: Andrey Borzenkov <arvidjaar@gmail.com>,
	Colin Watson <cjwatson@debian.org>
Subject: Re: btrfs subvolumes [was Re: Bugs and tasks for 2.02[~rc1] ]
Date: Mon, 18 Apr 2016 12:48:16 +0800	[thread overview]
Message-ID: <20160418044816.GA3747@linux-9gqx.suse> (raw)
In-Reply-To: <CAEaD8JNMkst6sOsk3YQZ39QVHyiwvqs9F8gCqBqn9rWtAokxnQ@mail.gmail.com>

On Mon, Apr 18, 2016 at 06:22:10AM +0200, Vladimir 'phcoder' Serbinenko wrote:
> On Wednesday, April 13, 2016, Olaf Hering <olaf@aepfle.de> wrote:
> 
> > On Fri, Mar 11, Vladimir 'phcoder' Serbinenko wrote:
> >
> > > On Wednesday, March 9, 2016, Olaf Hering <olaf@aepfle.de <javascript:;>>
> > wrote:
> > >     On Wed, Mar 02, Vladimir 'phcoder' Serbinenko wrote:
> > >     > I would like to come up with a complete list of 2.02 blockers in
> > one week
> > >     > time, so that we can have a reasonable timeline
> > >     Did anyone took the time to fix btrfs support (convert it from
> > handling
> > >     btrfs as filesystem into that what it really is: a container of
> > >     subvolumes)?
> > > What is the problem with current approach? subvolume is little more than
> > a
> > > directory from a point of view of read-only implementation
> >
> > A root filesystem in a subvolume is kind of a chroot. For example
> > grub.cfg within that subvolume references /boot/initrd. But upstream
> > grub can not use such grub.cfg via 'configfile ($root)$subvol/grub.cfg'
> > because the referenced path '/boot/initrd' does not take the subvolume
> > path into account.  This breaks at least in pvgrub, and makes testing
> > upstream grub with SLE12 or Leap impossible.
> >
> > Why does it break pvgrub? Both grub on BIOS and xen use the same
> convention

It won't. But we have been using relative patch schemes to support booting
subvolumes via btrfs set-default to rollback changes.

> 
> > The changes made by SUSE tweak grub2 enough to take subvolumes into
> > account. Not sure why these changes are missing upstream.

Because there's could only be one path scheme at a time and upstream has
decided to settle on absolute path. I think unless in config level could
provide means to deal with subvolumes and its mount point information there
couldn't be a clean solution for that.

Thanks,
Michael

> >
> > Olaf
> >
> > _______________________________________________
> > Grub-devel mailing list
> > Grub-devel@gnu.org <javascript:;>
> > https://lists.gnu.org/mailman/listinfo/grub-devel
> >
> 
> 
> -- 
> Regards
> Vladimir 'phcoder' Serbinenko

> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel



      reply	other threads:[~2016-04-18  4:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-18  4:22 btrfs subvolumes [was Re: Bugs and tasks for 2.02[~rc1] ] Vladimir 'phcoder' Serbinenko
2016-04-18  4:48 ` Michael Chang [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=20160418044816.GA3747@linux-9gqx.suse \
    --to=mchang@suse.com \
    --cc=arvidjaar@gmail.com \
    --cc=cjwatson@debian.org \
    --cc=grub-devel@gnu.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).