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.

Allow setting a pool to read-only-metadata mode.  This allows writes to the thins so long as they don't access unprovisioned areas.

Add for now lidbm function dm_tree_node_set_thin_pool_read_only()
with upstream patch.

https://www.redhat.com/archives/lvm-devel/2015-June/msg00054.html

Yet it's not quite clear what we should propose as lvm2 user API for this feature.

As the closest match with current lvm2 tools see we could see similarities with 'pvchange --allocateable y|n'.

So something like:  'lvchange --allocateable y|n  vg/pool' looks good - although the actual logic in thin-pool kernel target is slightly different, since kernel module avoid any modification of pool metadata - so it's not purely 'allocation related.

Other issue is - if user switch to 'read-only' mode - then ordinary filesystems do not handle well the case when some writes proceeds and some fail - but user should probably always use  'error-remount-ro' filesystem with thin volumes anyway.

For possible future enhancement cloned as upstream bug 1899206.