Bug 591861

Summary: vgscan (with cluster locking) doesn't remove filtered devices from .cache after filter change
Product: Red Hat Enterprise Linux 5 Reporter: Milan Broz <mbroz>
Component: lvm2-clusterAssignee: Milan Broz <mbroz>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: high Docs Contact:
Priority: high    
Version: 5.5CC: agk, antillon.maurizio, ccaulfie, cmarthal, coughlan, donhoover, dwysocha, heinzm, jbrassow, joe.thornber, mbroz, prockai, pvrabec
Target Milestone: rcKeywords: Regression, ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-01-13 22:44:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 592220    

Description Milan Broz 2010-05-13 11:35:31 UTC 
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):
lvm2-cluster-2.02.56-7.el5

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 13:00:15 UTC 
See also report here
https://www.redhat.com/archives/linux-lvm/2010-May/msg00012.html
Comment 3 Milan Broz 2010-05-13 15:00:34 UTC 
Fixed in upstream cvs -> POST for now.
Comment 5 Milan Broz 2010-05-14 09:42:19 UTC 
Fix in lvm2/lvm2-cluster-2.02.56-11.el5.
Comment 8 Corey Marthaler 2010-10-12 20:00:25 UTC 
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 22:44:07 UTC 
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.

http://rhn.redhat.com/errata/RHBA-2011-0053.html