All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: Sree Harsha Totakura <sreeharsha@totakura.in>, cjwatson@ubuntu.com
Subject: Re: Why ignore UUID when linux root device is an LV?
Date: Mon, 2 Jun 2014 19:33:20 +0400	[thread overview]
Message-ID: <20140602193320.43da908a@opensuse.site> (raw)
In-Reply-To: <20140502142330.GC7028@riva.ucam.org>

В Fri, 2 May 2014 15:23:30 +0100
Colin Watson <cjwatson@ubuntu.com> пишет:

> On Fri, May 02, 2014 at 02:54:13PM +0200, Sree Harsha Totakura wrote:
> > I would like to know why UUID is not used for root device in Linux
> > kernel's `root=' parameter when the root device uses LVM.
> 
> Filesystem UUIDs on LVM aren't necessarily unique in the presence of
> snapshots; and not all initramfses cope with root=UUID=* in any event,
> for instance:
> 
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612402
> 
> Every time this breaks in GRUB and we end up using UUIDs on LVM again, I
> get a slew of Debian bug reports until I figure it out and fix it.
> 

Note Debian Bug#747653 which results exactly from this behavior - btrfs
which spans multiple LVM volumes; grub hits LVM and does not use UUID
which results in passing multiple devices as root= argument.


> The LVM device names themselves are sufficiently stable that there
> should be no need to introduce additional layers of complexity by using
> filesystem UUIDs.  In general we only need them in cases where the
> device names are not stable.
> 
> > >From the commit log:
> > > commit 507736c87c49712ac618169d17a659bd6c25eecc
> > > Author: Colin Watson <cjwatson@ubuntu.com>
> > > Date:   Fri Jul 2 12:32:05 2010 +0100
> > > 
> > >     * util/grub-mkconfig_lib.in (uses_abstraction): New function.
> > >     * util/grub.d/10_linux.in: Use it to check for LVM, so that
> > >     LVM-on-RAID is handled correctly.
> > 
> > I see that this condition is added to address LVM/RAID configurations.
> > But, I guess it is similar to LVM/LUKS; is it not?
> 
> I'm not sure, but perhaps GRUB_ENABLE_CRYPTODISK=y would help
> grub-mkconfig notice this?
> 
> Regards,
> 



      reply	other threads:[~2014-06-02 15:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-02 12:54 Why ignore UUID when linux root device is an LV? Sree Harsha Totakura
2014-05-02 14:23 ` Colin Watson
2014-06-02 15:33   ` Andrey Borzenkov [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=20140602193320.43da908a@opensuse.site \
    --to=arvidjaar@gmail.com \
    --cc=cjwatson@ubuntu.com \
    --cc=grub-devel@gnu.org \
    --cc=sreeharsha@totakura.in \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.