Red Hat Bugzilla – Bug 591861
vgscan (with cluster locking) doesn't remove filtered devices from .cache after filter change
Last modified: 2013-02-28 23:09:04 EST
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.
See also report here
Fixed in upstream cvs -> POST for now.
Fix in lvm2/lvm2-cluster-2.02.56-11.el5.
Fix verified in lvm2-cluster-2.02.73-2.el5 (device was no longer listed in .cache file once filtered out and vgscan'ed).
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.