This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2222951 - RFE: support conversion of LV to thin LV by setting original LV as thin-pool data
Summary: RFE: support conversion of LV to thin LV by setting original LV as thin-pool ...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: lvm2
Version: 9.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Zdenek Kabelac
QA Contact: cluster-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-14 15:10 UTC by Zdenek Kabelac
Modified: 2023-09-23 19:15 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-23 19:15:53 UTC
Type: Story
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-8357 0 None Migrated None 2023-09-23 19:15:46 UTC
Red Hat Issue Tracker RHELPLAN-162392 0 None None None 2023-07-14 15:13:04 UTC

Description Zdenek Kabelac 2023-07-14 15:10:02 UTC 
Description of problem:

Users with existing data in i.e. Linear, Raid, VDO LVs may need to use then with thin-provisioning. While lvm2 already supports such user through 'external' origin, there could be cases where a direct conversion to thin-pool is better solutions.

To support this extend the 'lvconvert' with new supported conversion, that makes the original volume basically a 'data' volume for thin-pool and adds a thin volume with fully provisioned  volume mapping this data.

Such conversion should be possible to happen 'online' so user should not need to deactivate such LV.


Expected usage:

lvcreate -L10 -n normalLV  vgname

lvconvert --type thin  vgname/normalLV


Results with thin-pool with normalLV   being represented by thin.
Comment 2 Zdenek Kabelac 2023-07-14 15:12:22 UTC 
Upstream code already provides the initial support with some limitation.

Currently user has to manually 'extend' thin-pool if he want to use thin-pool for creation of futher thin LVs in the same pool.
Comment 4 Zdenek Kabelac 2023-07-14 15:15:58 UTC 
Also the primary use-case for this conversion can be seen by allowing to create multiple LVs within the single VDOPOOL.

User can convert 'VDOLV' into a thin volume with thin-pool having back-end in compressed deduplicated data volume handled by VDO target.
Comment 6 RHEL Program Management 2023-09-23 19:13:38 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 7 RHEL Program Management 2023-09-23 19:15:53 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.