Bug 591861 - vgscan (with cluster locking) doesn't remove filtered devices from .cache after filter change
vgscan (with cluster locking) doesn't remove filtered devices from .cache aft...
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: lvm2-cluster (Show other bugs)
All Linux
high Severity high
: rc
: ---
Assigned To: Milan Broz
Cluster QE
: Regression, ZStream
Depends On:
Blocks: 592220
  Show dependency treegraph
Reported: 2010-05-13 07:35 EDT by Milan Broz
Modified: 2013-02-28 23:09 EST (History)
13 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-01-13 17:44:07 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Milan Broz 2010-05-13 07:35:31 EDT
Description of problem:
vgscan should clean /etc/lvm/cache/.cache and refresh its contents according
to dev filter in lvm.conf.

This doesn't work with clustered lvm locking (only new devices are added).

User must manually remove .cache file to properly refresh filter.

Version-Release number of selected component (if applicable):

This is regression caused by commit c1b2049df907c0904faa07d01a23138b75dc3cfd

Version 2.02.56 - 
Move persistent filter dump to more appropriate place.
Comment 2 Milan Broz 2010-05-13 09:00:15 EDT
See also report here
Comment 3 Milan Broz 2010-05-13 11:00:34 EDT
Fixed in upstream cvs -> POST for now.
Comment 5 Milan Broz 2010-05-14 05:42:19 EDT
Fix in lvm2/lvm2-cluster-2.02.56-11.el5.
Comment 8 Corey Marthaler 2010-10-12 16:00:25 EDT
Fix verified in lvm2-cluster-2.02.73-2.el5 (device was no longer listed in .cache file once filtered out and vgscan'ed).
Comment 10 errata-xmlrpc 2011-01-13 17:44:07 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.