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 814732 - Extend lvconvert to construct thin pools from pre-formatted LVs
Summary: Extend lvconvert to construct thin pools from pre-formatted LVs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: lvm2
Version: 6.4
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: rc
: 6.4
Assignee: Zdenek Kabelac
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks: 812734 814777
TreeView+ depends on / blocked
 
Reported: 2012-04-20 14:51 UTC by Alasdair Kergon
Modified: 2013-02-21 08:09 UTC (History)
12 users (show)

Fixed In Version: lvm2-2.02.98-1.el6
Doc Type: Enhancement
Doc Text:
Feature: lvconvert has been enhanced to support conversion or pre-formatted LVs into a thin pool volume. With options --thinpool data_lv_name --poolmetadata metadata_lv_name user may use any pre-formatted LV to construct thin pool just like with lvcreate command. Reason: With lvcreate user could not have specify i.e. mirrored LV for metadata volume and it has been also complex, to guide allocation mechanism to use proper PVs for data and metadata LV. The lvconvert is easier to use for these cases.
Clone Of:
Environment:
Last Closed: 2013-02-21 08:09:23 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0501 0 normal SHIPPED_LIVE lvm2 bug fix and enhancement update 2013-02-20 21:30:45 UTC

Description Alasdair Kergon 2012-04-20 14:51:10 UTC 
Given an LV that contains data already in pool format, using lvconvert you can tell LVM to treat it as a pool and create LVs for any thin devices it contains.
Comment 1 Zdenek Kabelac 2012-04-27 14:20:00 UTC 
We may support here probably several ways:

Initialy we may add this support:


lvconvert   [-T|--thinpool     thinpool_lv] [--poolmetadatasize size | thinmetadata_lv] [--zero {y|n} |  --provisioned ] [--chunksize size]

User should be able to specify the LV that is should be used for the pool.

He may specify the size of the poolmetadata device, or it might be a second given LV (i.e. some mirrored LV), or it could be deduced with the same logic used in lvcreate (estimated from size of pool and chunksize and should fit 100MB)

Chunksize is either deduced to fit 100MB metadata size or given.

Zero means zeroing of provisioned blocks

Provisioned (or any better name?)  would create metadata with provisioned mapping of all blocks -  i.e.  user gives normal LV - and turns this LV in thin volume. Then he may extend the pool to add some snapshots for such LV...
Comment 2 Corey Marthaler 2012-07-26 20:46:15 UTC 
QE reviewed this BZ for QA_ACK but was unable to ack due to a lack of
requirements or description of how the new feature is supposed to work or be
tested.

Too many uncertainties in comment #1. Please add a more concrete definition of this feature as well as release criteria.

Please see
https://wiki.test.redhat.com/ClusterStorage/WhyNoAck
Comment 3 Corey Marthaler 2012-08-09 17:51:49 UTC 
QA planning phase ends Aug 10th (tomorrow), without more information this feature will likely be nacked by QA.

https://engineering.redhat.com/program/rhel/rhel-6-4-0/
Comment 4 Zdenek Kabelac 2012-08-10 08:40:07 UTC 
This feature should allow user to create thin pool data and metadata devices from already existing ones.

Thus user should be able to create  mirror/raid type LV and then use the command lvconvert to make it  thin data device or metadata device.

API from comment 1 might be slightly different.

Test should cover various scenarios - where mirror LVs are being turned into thin devices.

Key idea here is - user should be able to use mirrored  metadata device since the damage of metadata has serious impact on the stability of whole thinprovisiong - so using mirrored LVs  for metadata device is important for users.
Comment 5 Corey Marthaler 2012-08-15 22:11:52 UTC 
Adding QA ack for 6.4.

Devel will need to provide unit testing results however before this bug can be
ultimately verified by QA.
Comment 6 Zdenek Kabelac 2012-10-09 12:29:15 UTC 
lvconvert functionality has been updated upstream.

https://www.redhat.com/archives/lvm-devel/2012-October/msg00015.html

(see Bug 858874 for related problems)

Pre-formatted LVs should be convertible to thin pools with version 2.02.98
Comment 8 Nenad Peric 2012-10-31 11:40:11 UTC 
Based on tests for Bug 858874 and a thinp sanity test I am marking this BZ verified with same versions as the mentioned BZ.
Comment 9 errata-xmlrpc 2013-02-21 08:09:23 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-0501.html
Note You need to log in before you can comment on or make changes to this bug.