From: Milan Broz <mbroz@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Don Hoover <dxh@yahoo.com>
Subject: Re: [linux-lvm] lvdisplay ignoring filter in /etc/lvm.conf?
Date: Thu, 13 May 2010 13:39:35 +0200 [thread overview]
Message-ID: <4BEBE4F7.2040708@redhat.com> (raw)
In-Reply-To: <4BEAFFE5.3020406@redhat.com>
On 05/12/2010 09:22 PM, Milan Broz wrote:
> On 05/12/2010 05:56 PM, Don Hoover wrote:
>> On futher-further testing..it appears that a "vgscan -vvvvvvvvvvvvvv"
>> does not update the lvm cache like it used too before RHEL 5.5.
It is only cluster lvm problem,
I filled that problem here https://bugzilla.redhat.com/show_bug.cgi?id=591861
Add to cc if interested.
Workaround for now is to manually remove that .cache file after filter change.
Thanks for reporting this,
Milan
next prev parent reply other threads:[~2010-05-13 11:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 15:56 [linux-lvm] lvdisplay ignoring filter in /etc/lvm.conf? Don Hoover
2010-05-12 19:22 ` Milan Broz
2010-05-13 11:39 ` Milan Broz [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-05-12 15:10 Don Hoover
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=4BEBE4F7.2040708@redhat.com \
--to=mbroz@redhat.com \
--cc=dxh@yahoo.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).