Bug 1306717

Summary: LVM Thin: Integrate 'thin_ls' features into LVM
Product: Red Hat Enterprise Linux 7 Reporter: Jonathan Earl Brassow <jbrassow>
Component: lvm2Assignee: Zdenek Kabelac <zkabelac>
lvm2 sub component: Thin Provisioning QA Contact: cluster-qe <cluster-qe>
Status: CLOSED WONTFIX Docs Contact:
Severity: unspecified    
Priority: unspecified CC: agk, heinzm, jbrassow, msnitzer, prajnoha, thornber, zkabelac
Version: 7.2Keywords: FutureFeature
Target Milestone: rc   
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: 2020-08-21 20:58:54 UTC 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 Jonathan Earl Brassow 2016-02-11 16:21:26 UTC
'thin_ls' has the ability to tell how much space would be freed by a particular thinsnap removal and more.  Is there a suitable way to add this to LVM?

Comment 2 Peter Rajnoha 2016-08-19 13:13:38 UTC
*** Bug 1301623 has been marked as a duplicate of this bug. ***

Comment 3 Peter Rajnoha 2016-08-19 13:26:43 UTC
The problematic part here is that we need to get this information from thin_ls which is an external tool and which may take a long time to execute or it may run out of memory/swap. When doing any reporting, we're under a VG lock. So we'd need to find a way how to minimize the time that we spend under this VG lock. The per-LV lock would be much better here, but we don't have that in LVM at the moment.

So needs some thought on how should we handle this properly...