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.
DescriptionNathaniel Weddle
2019-02-25 17:26:41 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.03.02
How reproducible:
100%
Steps to Reproduce:
1. create thin pool with tmeta of 16GB
2. lvextend -L +30G /dev/mapper/vg-lv--pool_tmeta
3.
Actual results:
lvs output showing tmeta size change (because it is written into metadata), but dmsetup reports 16GB
Expected results:
lvextend command should probably fail, or at the very least, not write larger tmeta size to metadata.
Additional info:
Comment 2Alexandros Panagiotou
2020-11-25 17:27:03 UTC
Hello,
I have noticed this accidentally and it seems very similar to the discussion in BZ 1899798.
Kind Regards,
Alexandros
Comment 4RHEL Program Management
2021-02-01 07:37:06 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.