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.
Created attachment 1033257[details]
lvchange -vvvv
Description of problem:
After a pool corruption occurred (exhausted space), I got the pool working again by removing some LVs.
But I noticed that some commands where still missbehaving (i.e. I needed two runs two activate a thin LV), the first run failed with:
[fabiand@inner imgbased]$ sudo lvchange --activate y fedora/Image-0.1 -K
device-mapper: reload ioctl on failed: No data available
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Corrupt a thin pool
2. Create snapshots of a LV
3. Try to activate the device
Actual results:
Teh activation fails with the message above
Expected results:
Additional info:
It is one thing to fix the corruption, this bug is about explaining the error better.
Tool should better detect failing 'create' message and give a more explanatory error message here.
Comment 4RHEL Program Management
2020-12-15 07:34:38 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.
Created attachment 1033257 [details] lvchange -vvvv Description of problem: After a pool corruption occurred (exhausted space), I got the pool working again by removing some LVs. But I noticed that some commands where still missbehaving (i.e. I needed two runs two activate a thin LV), the first run failed with: [fabiand@inner imgbased]$ sudo lvchange --activate y fedora/Image-0.1 -K device-mapper: reload ioctl on failed: No data available Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Corrupt a thin pool 2. Create snapshots of a LV 3. Try to activate the device Actual results: Teh activation fails with the message above Expected results: Additional info: It is one thing to fix the corruption, this bug is about explaining the error better.