linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Goffredo Baroncelli <kreijack@libero.it>" <kreijack@libero.it>
Cc: cwillu <cwillu@cwillu.com>,
	helmut@hullen.de, linux-btrfs@vger.kernel.org
Subject: Re: R: Re: Subvolumes and /proc/self/mountinfo
Date: Wed, 20 Jun 2012 08:37:54 -0700	[thread overview]
Message-ID: <4FE1EE52.20002@zytor.com> (raw)
In-Reply-To: <32353828.234981340193742067.JavaMail.defaultUser@defaultHost>

On 06/20/2012 05:02 AM, Goffredo Baroncelli <kreijack@libero.it> wrote:
> 
> If I swap (via a rename) __active and __rollback, in the next boot my system
> uses a "good" copy of the root filesystem. This is a simple way to swap 
> two subvolumes, without involving the boot logic
> 
> Instead if I had tracked the subvolume-id, to swap the root filesystem I 
> would have update the boot logic.
> 
> I suspect that could exists other cases where it is preferable to track the 
> subvolume-id instead the path. However what I would highlight it is the two
> ways aren't equal.
> 

Yes.  The question here is what makes sense for the low-level part of a
bootloader (Syslinux in this case) to use, and it sounds like you have
some experience here that would be highly useful to have.

The thing to keep in mind here is that the low level bootloader code
*must* match what is installed in the boot block (functionally another
part of the bootloader), or all hell will break loose.  I think that
means that relying on the subvolume ID makes more sense.  To upgrade the
bootloader, invoke the bootloader installer at the end of the update;
that will repoint *everything*, which is rather nice.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


  reply	other threads:[~2012-06-20 15:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-20 12:02 R: Re: Subvolumes and /proc/self/mountinfo Goffredo Baroncelli <kreijack@libero.it>
2012-06-20 15:37 ` H. Peter Anvin [this message]
2012-06-20 16:34   ` Goffredo Baroncelli
2012-06-20 17:41     ` H. Peter Anvin
2012-06-20 18:06       ` Goffredo Baroncelli
2012-06-20 19:15         ` Helmut Hullen
2012-06-20 20:22           ` Goffredo Baroncelli
2012-06-20 21:49         ` H. Peter Anvin
2012-06-21  5:47           ` Goffredo Baroncelli
2012-06-21 11:46             ` Martin Steigerwald
2012-06-21 17:05               ` Goffredo Baroncelli
2012-06-21 13:38             ` H. Peter Anvin
2012-06-21 17:05               ` Goffredo Baroncelli
2012-06-21 17:11                 ` H. Peter Anvin
  -- strict thread matches above, loose matches on Subject: below --
2012-06-20 12:10 Goffredo Baroncelli <kreijack@libero.it>
2012-06-20 11:51 Goffredo Baroncelli <kreijack@libero.it>

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=4FE1EE52.20002@zytor.com \
    --to=hpa@zytor.com \
    --cc=cwillu@cwillu.com \
    --cc=helmut@hullen.de \
    --cc=kreijack@libero.it \
    --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).