From: Alasdair G Kergon <agk@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] WARNING: Ignoring duplicate config node: filter (seeking filter)
Date: Mon, 5 Mar 2007 19:35:51 +0000 [thread overview]
Message-ID: <20070305193551.GL3319@agk.surrey.redhat.com> (raw)
In-Reply-To: <20070305191635.75F0E7576E@mailer.at.ds9>
On Mon, Mar 05, 2007 at 08:16:35PM +0100, Cisco wrote:
> filter = [ "a/.*/", "r|/dev/cdrom|", "r|/dev/hda|", "r|/dev/hdb|",
> "r|/cdrom|" ]
Oops - the first pattern matches everything so the rest will have no effect:-)
The man page says:
filter -- List of patterns to apply to devices found by a scan.
Patterns are regular expressions delimited by any character and
preceded by a (for accept) or r (for reject). The list is tra-
versed in order, and the first regex that matches determines if
the device will be accepted or rejected (ignored). Devices that
don't match any patterns are accepted. If you want to reject
patterns that don't match, end the list with "r/.*/". If there
are several names for the same device (e.g. symbolic links in
/dev), if any name matches any a pattern, the device is
accepted; otherwise if any name matches any r pattern it is
rejected; otherwise it is accepted. As an example, to ignore
/dev/cdrom you could use: devices { filter=["r|cdrom|"] }
Alasdair
--
agk@redhat.com
next prev parent reply other threads:[~2007-03-05 19:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 18:00 [linux-lvm] WARNING: Ignoring duplicate config node: filter (seeking filter) Cisco
2007-03-05 18:19 ` David Brown
2007-03-05 19:16 ` AW: " Cisco
2007-03-05 19:35 ` Alasdair G Kergon [this message]
2007-03-05 20:56 ` AW: [linux-lvm] WARNING: Ignoring duplicate config node:filter " Cisco
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=20070305193551.GL3319@agk.surrey.redhat.com \
--to=agk@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;
as well as URLs for NNTP newsgroup(s).