From: Zdenek Kabelac <zkabelac@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: Lupin Deterd <lupindeterd@gmail.com>
Subject: Re: Controlling the sequence of dm-* creation
Date: Wed, 28 Nov 2012 11:07:43 +0100 [thread overview]
Message-ID: <50B5E26F.7040501@redhat.com> (raw)
In-Reply-To: <CAL0mBkTxqdmqd351VxkU1GLwfS_622OfS9wFCOkiWYKAhOAjow@mail.gmail.com>
Dne 28.11.2012 01:52, Lupin Deterd napsal(a):
> Hi,
>
> Is there a way to control how a dm- # devices created? e.g by udev or multipath?
>
> Let say, I wanted to have my dm- devices created for multipath devices
> to start only on dm-7 to dm-9, instead of using lower numbered
> dm-[0-8] as it's been mapped to a different lun. Is this possible?
You cannot control the order of 'dm-X' devices (they are created in kernel).
Actually you should never ever use these names in userspace anywhere - since
they are pretty random.
You should reference your devices via UUID or VG/LV names in case you are
using lvm.
Zdenek
next prev parent reply other threads:[~2012-11-28 10:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 0:52 Controlling the sequence of dm-* creation Lupin Deterd
2012-11-28 10:07 ` Zdenek Kabelac [this message]
2012-11-28 10:45 ` Peter Rajnoha
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=50B5E26F.7040501@redhat.com \
--to=zkabelac@redhat.com \
--cc=dm-devel@redhat.com \
--cc=lupindeterd@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox