From: "Bryn M. Reeves" <bmr@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] device filter in lvm.conf
Date: Wed, 12 Nov 2008 18:12:45 +0000 [thread overview]
Message-ID: <491B1C9D.3090401@redhat.com> (raw)
In-Reply-To: <B668DE010628694A85EC2A4C53DCF769261FA0D8@SA000011>
Tuncel.Mutlu@akbank.com wrote:
> filter = [ "a/sda[1-9]$/" "a/sddlm*/" "r/.*/" ]
>
> and types row has been added
>
> types = [ "sddlmfdrv", 16 ]
>
> This has been known to work on another Linux box, but not here. How must I
> alter the filter so the LVM should accept sda and sddlm devices but reject
> all others ?
When you say it doesn't work on this box, what actually happens? Do you
fail to filter out the individual paths, or do you fail to include the
multipath device that you want to use?
You may find that removing the cache (/etc/lvm/cache/.cache) after
editing the filters straightens things out (this should be automatic but
I've found that on some releases I've needed to manually remove it).
Also, is the filter really what you wanted?
> filter = [ "a/sda[1-9]$/" "a/sddlm*/" "r/.*/" ]
^^^^^^^^
This says to accept devices that have a string "sddl" followed by any
zero or more "m" characters. I don't know the naming scheme for HDLM,
but your example implies that they'd follow a pattern of
sddlm[a-z][a-z], or something.
Perhaps "a/sddlm.*/" would work better (sddlm followed by any number of
any character), since you're unlikely to have other device nodes with a
prefix of sddlm. You could tighten that up further as: "a|/dev/sddlm.*|"
if you liked (lvm filter expressions work like sed - you can uniformly
replace the '//' delimiters with other chars - I like pipes as it means
you need less \/ escaping when using paths).
Regards,
Bryn.
next prev parent reply other threads:[~2008-11-12 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 17:58 [linux-lvm] device filter in lvm.conf Tuncel.Mutlu
2008-11-12 18:12 ` Bryn M. Reeves [this message]
2008-11-12 18:29 ` Tuncel.Mutlu
2008-11-12 19:06 ` Bryn M. Reeves
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=491B1C9D.3090401@redhat.com \
--to=bmr@redhat.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