All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Rajnoha <prajnoha@redhat.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Changes in device-mapper and LVM2 that can affect grub's functionality
Date: Wed, 09 Sep 2009 14:01:36 +0200	[thread overview]
Message-ID: <4AA79920.9030506@redhat.com> (raw)
In-Reply-To: <1252491992.2998.11.camel@fz.local>

On 09/09/2009 12:26 PM, Felix Zielcke wrote:
> What's the point in having the /dev/dm-X devices at all?
> Does anything use them?

...nothing uses them and nothing ever should! These names are not
stable (the number depends on the activation sequence of those
devices). Not usable for anything, really, just to keep udev guys
happy :)

Actually, we wanted to abandon these nodes first, so they would never
be visible under /dev. And keep the old way instead.

But when we discussed this with Kay Sievers from udev:

"In general we do not want any unneeded disconnect from kernel names
and /dev names, and dm block devices should stay as /dev/dm-* device
nodes."

"Please do not rename kernel devices, they should match the kernel
names. Only create SYMLINK+= to the kernel names..."

"Sure, but there is still not enough reason to be different from the
kernel name. You support rename, that should never happen, that a device
node needs to be renamed, if the kernel does not change the device name."

"Sounds fine, as long as the /dev names match the kernel devices."

"There is the rule, that kernel block device names and /dev names match,
and the kernel log shows device names which translate directly to the
primary device nodes. DM is not an exception here, all block device
behave like that , and we like to continue that, and not make needless
rules just to be special here."

...and so on and on...

(the whole discussion is at http://markmail.org/message/bj4zkjo2peeocnhq)

> Currently all symlinks are ignored.
> If we use the target of the /dev/mapper/* symlinks, i.e. a /dev/dm-X
> device this would at least with the default Debian initrd not work and I
> doubt the responding persons for this will change this ever. Even
> root=UUID= isn't working for LVM devices, because only the root LV is
> activated and not all inside the initrd.
> 
> If we would use the symlink itself for root= it could break if there
> were symlinks which aren't inside the initrd too.
> 
> I personally don't like this change at all.
> Why not just remove the dm-X devices and make the /dev/mapper/ ones the
> only and real ones?

...we would like to, but...

> Maybe the udev maintainers just prefer cryptic numbers for every real
> device and only accept symlinks for descriptive ones.

Yes, that's the case.

OK, I'll try to talk with Kay again and discuss all the problems that
this "udev law" brings in real-life situations for dm devices and
everything using it.

I just needed your opinion, too, thanks! So maybe we have one more
argument against such layout for udev guys...

Peter



  reply	other threads:[~2009-09-09 12:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-09 10:01 Changes in device-mapper and LVM2 that can affect grub's functionality Peter Rajnoha
2009-09-09 10:26 ` Felix Zielcke
2009-09-09 12:01   ` Peter Rajnoha [this message]
2009-10-12 12:19     ` Felix Zielcke

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=4AA79920.9030506@redhat.com \
    --to=prajnoha@redhat.com \
    --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 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.