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:

With new introduced support for error_when_full we now get into 2 different cases.
When thin pool is overfilled with data - we could end in  'out_of_data_space' mode when error when full is set -  or  in  'ro' mode otherwise (after target timeout).

'ro' mode doesn't accept i.e. delete messages and needs different lvm2 handling for basically same situation  (pool is out of data space).

Version-Release number of selected component (if applicable):
lvm2: 2.02.116
kernel thin pool target: v1.14.0

How reproducible:


Steps to Reproduce:
1. create pool with different  --errorwhenfull settings
2. overfill pool and check pool status
3.

Actual results:


Expected results:


Additional info:

This was fixed via bug#1243913 with "dm thin: stay in out-of-data-space mode once no_space_timeout expires"

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