Bug 1351777

Summary: dmeventd should be notified about metadata change
Product: [Community] LVM and device-mapper Reporter: Zdenek Kabelac <zkabelac>
Component: lvm2Assignee: LVM Team <lvm-team>
lvm2 sub component: dmeventd QA Contact: cluster-qe <cluster-qe>
Status: NEW --- Docs Contact:
Severity: unspecified    
Priority: medium CC: agk, heinzm, jbrassow, pasik, prajnoha, zkabelac
Version: 2.02.152Flags: rule-engine: lvm-technical-solution?
rule-engine: lvm-test-coverage?
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Zdenek Kabelac 2016-06-30 19:55:42 UTC 
Description of problem:

dmeventd thin plugin stops retrying resize of thin pool if there is a failure - to avoid stopping filling system logs with lots of failures and archives.

However when the VG is i.e. extended with a new space, there is currently no mechanism to let know dmeventd there is new chance to 'resize'.

ATM user has to manually at least run 'vgchange --refresh' after i.e. 'vgextend' or even 'lvremove'

So the purpose of BZ is provide some solution here.

As a proposal seems to be a reuse of mechanism used for update of lvmetad,
where before drop of VG lock lvmetad is updated.



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

How reproducible:


Steps to Reproduce:
1. let resize fail because there is no space in vg 
2. add new space
3. resize will not happen anyway

Actual results:


Expected results:


Additional info: