From: Joe Julian <me@joejulian.name>
To: dm-devel@redhat.com
Subject: Re: udev rules do not create partition entries when an lvm lv is partitioned
Date: Fri, 4 Sep 2015 12:34:16 -0700 [thread overview]
Message-ID: <55E9F238.8080004@joejulian.name> (raw)
In-Reply-To: <20150904191209.GA8446@localhost.localdomain>
On 09/04/2015 12:12 PM, Bryn M. Reeves wrote:
> On Fri, Sep 04, 2015 at 11:18:26AM -0700, Joe Julian wrote:
>> Yes, I'm aware of all the arguments against even doing this, but I have my
>> reasons for doing it this way.
>>
>> When you create a partition on an lv:
>>
>> sgdisk /dev/vg1/lv1 -n 0:0:0
>>
>> there is no udev rule to create the partition entry, '/dev/vg1/lv1p1' (for
>> instance). For my immediate use case, this causes ceph-disk to fail as it
>> cannot find the partition as it's expecting to find the device name with a
>> new "1" at the end. Any suggestions on how I could make this happen?
> Why not just name the LV lv1p1 if ceph-disk is hard wired to expect that
> naming?
>
> There's not a lot of benefits to using partitions on top of logical
> volumes and if you're not expecting them they can be problematic (e.g.
> when they are the partitions of a running VM that is also accessing the
> disk).
>
> It is possible to create partitions on pretty much any device-mapper
> device using the normal tools and then create new dm devices to map the
> partitions using kpartx.
>
> Multipath-tools supplies udev rules to automate this so that the
> partition maps are created automatically by udev (since it works with
> whole disks): you could use that as an example if you really want to try
> that approach but it's fairly easy to get the rules wrong in subtle ways
> that may prevent booting.
>
> If you just want a temporary mapping to set things up run:
>
> # kpartx -a /dev/vg1/lv1
>
> And you should find partition maps at /dev/mapper/vg1-lv1p1 etc.
>
> kpartx -d to remove.
>
> Regards,
> Bryn.
>
I've looked at the ceph-disk source. It's expecting whatever device path
I give it to add r".*1" as it (ceph-disk) creates the partitions so a
naming trick isn't going to work. There's no chance during the process
to manually add dm mappings or use kpartx.
And like I said, I'm aware that there's either not a lot of benefits, or
no benefit, to using partitions on top of logical volumes. Ceph has a
very complex configuration and installation, so redoing that seems like
it would be a much more cumbersome task over just making partition
mappings work.
prev parent reply other threads:[~2015-09-04 19:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 18:18 udev rules do not create partition entries when an lvm lv is partitioned Joe Julian
2015-09-04 19:12 ` Bryn M. Reeves
2015-09-04 19:34 ` Joe Julian [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=55E9F238.8080004@joejulian.name \
--to=me@joejulian.name \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).