Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionJonathan Earl Brassow
2014-11-17 21:40:50 UTC
Import existing LVs into a thin pool, removing any 'holes' in the process (and deduplicating).
- Take existing LV and existing LV pool. Append the data extents LV to the pool data.
- Call a script that takes the range of block numbers and adds it to existing thin metadata as a new LV.
Once the LV is in the thin pool, it is possible to discard unused blocks and reclaim them for further use.
Comment 1Heinz Mauelshagen
2016-10-04 12:47:07 UTC
(In reply to Jonathan Earl Brassow from comment #0)
> Import existing LVs into a thin pool, removing any 'holes' in the process
> (and deduplicating).
> - Take existing LV and existing LV pool. Append the data extents LV to the
> pool data.
>
> - Call a script that takes the range of block numbers and adds it to
> existing thin metadata as a new LV.
>
>
> Once the LV is in the thin pool, it is possible to discard unused blocks and
> reclaim them for further use.
The to be imported early provisioned LV (i.e. non-thin LV) doesn't have to be inactive during the process, in which case we'd need to add all of its allocated extents to the thin pool, create the fully provisoned thin mapping tree for the LV, update and reload thus trimming the new thin LV as a last step.
For completenes:
in case of such LV being inactive/frozen, we can remove any completely trimmable extents in the first step, thus freeing up space sooner. This approach heavily depends on the locality of any data/metadata on the fatLV relative to the extent size and may result in little early savings worst case.
Comment 4RHEL Program Management
2020-12-15 07:31:56 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.