All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Peter Rajnoha <prajnoha@redhat.com>
Cc: henson@acm.org, linux-lvm@redhat.com
Subject: Re: [linux-lvm] Identifying useable block devices
Date: Fri, 17 Jan 2014 10:29:21 +0100	[thread overview]
Message-ID: <20140117092921.GA5869@x2.net.home> (raw)
In-Reply-To: <52D8E1A7.1080506@redhat.com>

On Fri, Jan 17, 2014 at 08:54:15AM +0100, Peter Rajnoha wrote:
> On 01/16/2014 10:03 PM, Paul B. Henson wrote:
> >> Peter Rajnoha
> >> Sent: Wednesday, January 15, 2014 9:43 PM
> >>
> >> This applies only if the symlinks/nodes are created directly with
> >> libdevmapper - which is the old classical way.
> >> If udev is used to manage /dev
> >> content for dm/lvm devices then the /dev/vg/vol is a symlink to /dev/dm-X
> >> (also /dev/mapper/vg-vol is a symlink to /dev/dm-X). And dm-X is not a
> > 
> > Hmm, yah, I see on my RHEL6 boxes that is indeed the case, as opposed to my
> > older RHEL5 boxes.
> > 
> >> As for mount, findmnt and other utilities from util-linux - they all use
> >> one common code which can handle this situation (e.g. if you call
> >> "findmnt /dev/vg/vol", it shows you /dev/mapper/vg-vol on output, not
> >> the dm-X the /dev/vg/vol is referencing actually).
> > 
> > IIRC, this thread started when somebody was being advised *not* to use the
> > /dev/mapper path, but rather to use the /dev/vg path. If there is special
> > case handling in util-linux, why isn't it returning what is being advertised
> > as the preferable path to use rather than the one that is said to be
> > internal and not to be referenced?
> 
> Well, that is probably an RFE for util-linux to give priority to
> /dev/<vgname>/<lvname> instead of /dev/mapper/<vgname>-<lvname>
> if it's available...
> 
> Karel, would that be possbible for you to add? (though I expect
> you probably don't want to add any additional and specific logic
> for dm devices :) )

I have spent years to move from /dev/dm-N to /dev/mapper/<name> ... :-)

Note that /dev/mapper/<name> paths are in many cases composed from
/sys/block/dm-<N>/dm/name and this sysfs file has been added (by
Milan) just to support conversion from random DM paths (or devno) to
the canonicalized /dev/mapper/<name>.

How I can convert maj:min or /dev/dm-N to /dev/vg/vol path? Is the
volume group name (always) in /sys/block/dm-<N>/dm/name and (always)
separated by "-" ?

It also seems that this is LVM specific, for non-LVM devices (for 
example LUKS) we want to use /dev/mapper/<name>.

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

  reply	other threads:[~2014-01-17  9:29 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-15  8:19 [linux-lvm] Identifying useable block devices Marius Vollmer
2014-01-15 15:49 ` Alasdair G Kergon
2014-01-15 16:17 ` Oliver Rath
2014-01-15 20:24   ` Anatoly Pugachev
2014-01-16  1:32     ` Paul B. Henson
2014-01-16  5:42       ` Peter Rajnoha
2014-01-16 21:03         ` Paul B. Henson
2014-01-17  7:54           ` Peter Rajnoha
2014-01-17  9:29             ` Karel Zak [this message]
2014-01-17  9:53               ` Peter Rajnoha
2014-01-16  6:04 ` Peter Rajnoha
2014-01-17 10:02 ` Marius Vollmer
2014-01-17 13:35   ` Marius Vollmer
2014-01-20 11:52     ` Peter Rajnoha
2014-01-20 11:49   ` Peter Rajnoha
2014-01-20 12:02     ` Peter Rajnoha
2014-01-22  9:23       ` Marius Vollmer
2014-01-23 11:42         ` Peter Rajnoha
2014-01-23 12:35           ` Marius Vollmer
2014-01-24 13:24             ` Peter Rajnoha
2014-01-24 13:29               ` Peter Rajnoha
2014-01-24 14:39                 ` Marius Vollmer
2014-01-24 15:02                   ` Peter Rajnoha
2014-01-27  7:37                     ` Marius Vollmer
2014-01-24 14:50               ` Marius Vollmer
2014-01-24 15:08                 ` Peter Rajnoha
2014-01-24 15:17                 ` Zdenek Kabelac
2014-01-24 15:20                   ` Peter Rajnoha
2014-01-22  9:02     ` Marius Vollmer

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=20140117092921.GA5869@x2.net.home \
    --to=kzak@redhat.com \
    --cc=henson@acm.org \
    --cc=linux-lvm@redhat.com \
    --cc=prajnoha@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.