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.

Bug 1441153

Summary: Thin-pool using ~16GB of metadata uses different limit for lvm2 and thin tools
Product: Red Hat Enterprise Linux 7 Reporter: Zdenek Kabelac <zkabelac>
Component: lvm2Assignee: Zdenek Kabelac <zkabelac>
lvm2 sub component: Thin Provisioning QA Contact: cluster-qe <cluster-qe>
Status: CLOSED WONTFIX Docs Contact:
Severity: unspecified    
Priority: urgent CC: agk, bubrown, cmarthal, heinzm, jbrassow, loberman, mgandhi, msnitzer, nkshirsa, prajnoha, revers, rhandlin, thornber, zkabelac
Version: 7.4   
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:
: 1909699 (view as bug list) Environment:
Last Closed: 2020-11-04 15:55:49 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:
Bug Depends On:    
Bug Blocks: 1909699    

Description Zdenek Kabelac 2017-04-11 10:42:15 UTC 
Description of problem:

When using lvm2 with 16GB (max size) of thin-pool metadata, several operations are not combining well together.

It is allowed to create bigger metadata LV then the size accepted by kernel which does require to not pass bigger device - otherwise messages are thrown back to user from kernel.

Problem could be easily seen when user is passing 16GB LV to thin_restore and then using this 'restored' LV  via lvconvert as a thin-pool metadata LV.


Version-Release number of selected component (if applicable):
2.02.169

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 11 Zdenek Kabelac 2021-02-01 14:39:56 UTC 
Solved also in stable-2.02 patch set:

https://www.redhat.com/archives/lvm-devel/2021-February/msg00015.html
https://www.redhat.com/archives/lvm-devel/2021-February/msg00017.html
https://www.redhat.com/archives/lvm-devel/2021-February/msg00016.html

Introduce   allocation/thin_pool_crop_metadata  with default value 0

If users wants 'cropping' to 15.81GiB he must set the value =1 - otherwise new lvm2 will use full available amount for thin-pool allocation 15.88GiB.