Bug 1372786 - lvmetad: better update mechanism of metadata caching
Summary: lvmetad: better update mechanism of metadata caching
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: LVM and device-mapper
Classification: Community
Component: lvm2
Version: 2.02.166
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: LVM and device-mapper development team
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-02 16:44 UTC by Zdenek Kabelac
Modified: 2019-08-19 22:22 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-19 22:22:37 UTC
rule-engine: lvm-technical-solution?
rule-engine: lvm-test-coverage?


Attachments (Terms of Use)

Description Zdenek Kabelac 2016-09-02 16:44:18 UTC
Description of problem:

This bugzilla should serve as a placeholder for improvement of lvmetad.

At this moment we are struggling on initial 'pvscan --cache' which actually does whole 'internal' scan anyway - so avoid usage of deadlock when reading devices ourself.

Also we want to allow 'autoactivation'  without actually having 'lvmetad' running.

We should have clear  'state-machine' which does not miss any state change of device and yet doesn't require our tool to 'scan' all system devices.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:


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