From: Oliver Rath <rath@mglug.de>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] unwanted autocreation of /dev/mapper/ entries while using parted on lvm devices
Date: Mon, 24 Feb 2014 13:17:39 +0100 [thread overview]
Message-ID: <530B3863.8090504@mglug.de> (raw)
In-Reply-To: <530B059F.3060502@redhat.com>
Hi Peter,
thanks for your reply!
Am 24.02.2014 09:41, schrieb Peter Rajnoha:
> On 02/23/2014 11:36 PM, Oliver Rath wrote:
>> [..]
> 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.
>
Ist it possible to avoid this /dev/mapper-generation, if I partitioning
lvm-devices? My problem ist, that Im not able to export the whole device
i.e. as iscsi, if some sub-device is mapped in /dev/mapper/... (says,
its busy then ..).
At the moment I always have to delete these subdevices via kpartx -d
/dev/myvg/.. (or dmsetup remove ..) before exporting it, which is a bit
annoying.
I took a look into 10-dm.rules, but have no idea, what to do.
Regards,
Oliver
next prev parent reply other threads:[~2014-02-24 12:17 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
2014-02-24 12:17 ` Oliver Rath [this message]
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=530B3863.8090504@mglug.de \
--to=rath@mglug.de \
--cc=linux-lvm@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.