From: Peter Rajnoha <prajnoha@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: rath@mglug.de
Subject: Re: [linux-lvm] unwanted autocreation of /dev/mapper/ entries while using parted on lvm devices
Date: Mon, 24 Feb 2014 09:41:03 +0100 [thread overview]
Message-ID: <530B059F.3060502@redhat.com> (raw)
In-Reply-To: <530A77EC.5090900@mglug.de>
On 02/23/2014 11:36 PM, Oliver Rath wrote:
> Hi List,
>
> Im not sure, if the udev-rules of lvm is creating this. Im Using Ubuntu
> 12.04.4 + lvm git yesterday, compiles with --enable-udev_sync
> --enable-udev_rules. Here my testing results:
>
>
> root@dmicrash\:rules.d# vgcreate myvg /dev/sdc1 /dev/sdd1
> Volume group "myvg" successfully created
> root@dmicrash\:rules.d# lvcreate --name test --size 20G myvg
> Logical volume "test" created
> root@dmicrash\:rules.d# parted /dev/myvg/test mklabel msdos
>
> root@dmicrash\:rules.d# parted /dev/myvg/test mkpart primary 0% 40%
>
> root@dmicrash\:rules.d# ls /dev/mapper/
> control myvg-test myvg-test1
>
> The device myvg-test1 was created automatically (normally this is done
> by kpartx?). I disabled gnome-automounter, didnt help.
>
> I tried to monitor this with udevadm --monitor, but i didnt get
> displayed the rule-file who did this.
>
> Any hints?
The parted itself creates a new device-mapper mapping that represents
the partition. Then it's like any other device-mapper device and so
the /dev content is created by 10-dm-disk.rules (the /dev/mapper
content) and 13-dm-disk.rules (the /dev/disk content).
Parted has this functionality integrated so there's no need to call
kpartx in addition.
--
Peter
next prev parent reply other threads:[~2014-02-24 8:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-23 22:36 [linux-lvm] unwanted autocreation of /dev/mapper/ entries while using parted on lvm devices Oliver Rath
2014-02-24 8:41 ` Peter Rajnoha [this message]
2014-02-24 12:17 ` Oliver Rath
2014-02-24 12:40 ` [linux-lvm] [SOLVED] " Oliver Rath
2014-02-24 13:09 ` 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=530B059F.3060502@redhat.com \
--to=prajnoha@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=rath@mglug.de \
/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).