All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Loïc Minier" <lool+redhat@via.ecp.fr>
To: dm-devel@redhat.com
Subject: Re: Weird discrepancy between /dev/mapper/* and /dev/dm-* devices breaks lilo
Date: Wed, 31 Jan 2007 16:47:32 +0100	[thread overview]
Message-ID: <20070131154732.GC27755@bee.dooz.org> (raw)
In-Reply-To: <20070131151059.GC21980@agk.surrey.redhat.com>

On Wed, Jan 31, 2007, Alasdair G Kergon wrote:
> >  Or is the device-mapper code supposed to accept device names from /dev
> >  as parameters?
> It does not do that at the moment.  Perhaps there's a case for adding
> inode->device number conversions to dmsetup: You're the first person
> to suggest this.

 Ok; lilo isn't calling the dmsetup command, but uses libdevmapper
 directly, so even if you add support for any /dev device name in
 dmsetup, it wont help lilo.  Hence, I've changed the problematic dm
 task call to use major/minor instead of the name (see attached patch)
 and will wait for feedback from users as I don't have such a setup.

 So, thanks for clarifying this!  I'm not sure it would be a good idea
 to accept device mapper names as well as /dev names in dmsetup as I
 think this would confuse things.  I personally like it that dmsetup
 reflects what the ioctl accepts, nothing more, nothing less.


PS: I was wrong when saying that the code is in a Debian specific patch,
the patch is only historic and the problematic code is in the lilo
mainline
-- 
Loïc Minier <lool@dooz.org>

  reply	other threads:[~2007-01-31 15:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-31 10:47 Weird discrepancy between /dev/mapper/* and /dev/dm-* devices breaks lilo Loïc Minier
2007-01-31 11:00 ` Loïc Minier
2007-01-31 15:10   ` Alasdair G Kergon
2007-01-31 15:47     ` Loïc Minier [this message]
2007-01-31 15:06 ` Alasdair G Kergon
2007-01-31 15:54   ` Loïc Minier
2007-01-31 20:10     ` Luca Berra

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=20070131154732.GC27755@bee.dooz.org \
    --to=lool+redhat@via.ecp.fr \
    --cc=dm-devel@redhat.com \
    /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.