From: "Cisco" <cisco66@gmx.de>
To: linux-lvm@redhat.com
Subject: [linux-lvm] WARNING: Ignoring duplicate config node: filter (seeking filter)
Date: Mon, 5 Mar 2007 19:00:25 +0100 [thread overview]
Message-ID: <20070305180020.005367576E@mailer.at.ds9> (raw)
Hi all,
after upgrading (compiling from source)LVM2 and device
mapper, i always get the warning message "WARNING: Ignoring
duplicate config node: filter (seeking filter)" when doing
"lvm version" or any other lvm command.
Does anyone know what's going on and if i should be
concerned about this, or even better: What is the meaning of
this message and how can i get rid of it.
Thanks in advance and best regards.
Kernel: 2.6.20, Debian unstable
LVM version: 2.02.22 (2007-02-13)
Library version: 1.02.18 (2007-02-13)
Driver version: 4.11.0
next reply other threads:[~2007-03-05 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 18:00 Cisco [this message]
2007-03-05 18:19 ` [linux-lvm] WARNING: Ignoring duplicate config node: filter (seeking filter) David Brown
2007-03-05 19:16 ` AW: " Cisco
2007-03-05 19:35 ` Alasdair G Kergon
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=20070305180020.005367576E@mailer.at.ds9 \
--to=cisco66@gmx.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 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).