Bug 1306717 - LVM Thin: Integrate 'thin_ls' features into LVM
Summary: LVM Thin: Integrate 'thin_ls' features into LVM
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: lvm2
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Zdenek Kabelac
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
: 1301623 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-11 16:21 UTC by Jonathan Earl Brassow
Modified: 2021-09-03 12:51 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-08-21 20:58:54 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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...
Note You need to log in before you can comment on or make changes to this bug.