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.

Description of problem:

As discussed on https://docs.google.com/document/d/15J2tSBc3scl_Gtl4dbhFUe6ApPo90yrlAJZ6e59i4z0 point 2, we must force (or at least strongly warn) users to grow metadata manually too, if they manually grow the thinpool data using lvextend. This will prevent metadata full issues in the future.

Additional info:

Many gluster customers have small pools created by default scripts during setup, and have autoextend turned off by design, because gluster wants to be in control of the storage allocation, and doesn't allow autoextension because that would circumvent their storage manager. This results in customers manually increasing data subsequently, but many times forgetting to increase metadata too. Eventually metadata reaches 100% and thinpool corruptions ensue.

From backported commit 515867bbad4565b788460b1fc8cfe91acd5ade1e 
https://www.redhat.com/archives/lvm-devel/2019-April/msg00003.html

lvm2 automatically tries to upsize thin-pool metadata to match the growth of thin-pool data size.

Closing as duplicate of bug 1610260 which is already fixed for RHEL 7.6

*** This bug has been marked as a duplicate of bug 1610260 ***