From: Erik Schwalbe <erik.schwalbe@canoo.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Hide volume group during startup
Date: Thu, 12 Apr 2012 14:14:08 +0200 (CEST) [thread overview]
Message-ID: <1943758108.360003.1334232848115.JavaMail.root@nelson.canoo.com> (raw)
In-Reply-To: <4F86C1F4.4080809@redhat.com>
Hi,
there is only one dm-device in /dev:
...
drwxr-xr-x 5 root root 100 2012-04-05 12:50 disk
brw-rw---- 1 root disk 251, 18 2012-04-05 12:51 dm-18
drwxr-xr-x 4 root root 80 2012-04-05 12:51 drbd
...
/dev/data/kvm_disk0 is a blockdevice for drbd, so there are many drbd files in /dev
...
brw-rw---- 1 root disk 147, 20 2012-04-08 11:48 drbd20
...
drbd20 is the drbd resource using kvm_disk0 as device.
The symlink in /dev/data/ is:
lrwxrwxrwx 1 root root 24 2012-04-05 12:51 kvm_disk0 -> ../mapper/data-kvm_disk0
Should I be using this:
filter = [ "r|/dev/mapper/data-kvm_disk0|", "r|/dev/kvm_disk0|", "a|.*|"]
I know, it is a little bit confusing.
The LV in VG data is called kvm_disk0 and the VG initiated on this device is also called kvm_disk0.
Sorry, but thank you for help.
Regards,
Erik
----- Original Message -----
From: "Bryn M. Reeves" <bmr@redhat.com>
To: "LVM general discussion and development" <linux-lvm@redhat.com>
Cc: "Erik Schwalbe" <erik.schwalbe@canoo.com>
Sent: Thursday, 12 April, 2012 1:52:20 PM
Subject: Re: [linux-lvm] Hide volume group during startup
On 04/12/2012 12:41 PM, Erik Schwalbe wrote:
> Hi,
>
> filter was:
>
> filter = [ "r|/dev/data/kvm_disk0|" ]
>
> path:
> /dev/data/kvm_disk0 -> ../mapper/data-kvm_disk0
To filter a device-mapper device you also have to filter out the
/dev/dm-N device nodes that udev manages. There's also a symlink from
/dev/$VG_NAME/$LV_NAME to the dm-N node (although I think that should be
handled by filtering /dev/dm-N).
I'd be using something like:
[ "r|/dev/dm.*|", "r|/dev/$VG_NAME|", "a|.*|"]
Alternately (and I prefer this for many configurations) you can accept
("a|..|") the device you need for the data VG and reject all other
devices ("r|.*|").
> The device name is stable, but what other way of control activation are possible??
Tags but since you're not currently filtering dm-N nodes I would try
that first.
Regards,
Bryn.
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next prev parent reply other threads:[~2012-04-12 12:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2049162317.298117.1334137791059.JavaMail.root@nelson.canoo.com>
2012-04-11 10:04 ` [linux-lvm] Hide volume group during startup Erik Schwalbe
2012-04-12 11:11 ` Bryn M. Reeves
2012-04-12 11:41 ` Erik Schwalbe
2012-04-12 11:52 ` Bryn M. Reeves
2012-04-12 12:14 ` Erik Schwalbe [this message]
2012-04-12 12:26 ` Bryn M. Reeves
2012-04-12 13:31 ` Erik Schwalbe
2012-04-12 13:39 ` Bryn M. Reeves
2012-04-12 14:14 ` Erik Schwalbe
2012-04-12 14:30 ` Bryn M. Reeves
2012-04-12 14:50 ` Erik Schwalbe
2012-04-12 12:01 ` Lars Ellenberg
2012-04-12 12:33 ` Erik Schwalbe
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=1943758108.360003.1334232848115.JavaMail.root@nelson.canoo.com \
--to=erik.schwalbe@canoo.com \
--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 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).