Bug 1358314 - [RFE] Provide mechanism for lvs output with flush
Summary: [RFE] Provide mechanism for lvs output with flush
Keywords:
Status: NEW
Alias: None
Product: LVM and device-mapper
Classification: Community
Component: lvm2
Version: 2.02.161
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: LVM Team
QA Contact: cluster-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-20 13:40 UTC by Zdenek Kabelac
Modified: 2023-08-10 15:40 UTC (History)
6 users (show)

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

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1368020 1 None None None 2021-09-03 12:41:53 UTC

Internal Links: 1368020

Description Zdenek Kabelac 2016-07-20 13:40:20 UTC 
Description of problem:

Recent versions of lvm2 finally fixed some unwanted dm status calls with flushing, so upon normal operation lvm2 command should not 'deadlock' while flushing thin-pool or a cache device and holding  VG lock potentially endlessly.

However user may have requirement to see 'flushed' output purely via lvm2 command. So we need a mechanism to flush a device outside locked section and report the results of this operation.

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.