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.
I think you'd need to do a force detach for this since it won't be possible to write back the content of a missing writecache. The ability to force detach a cachevol is covered in bug 1915492. In terms of usage you'd just add the --force option to the command, which will skip any attempt to write back the cache before detaching.
The fix for bug 1915492 is:
https://sourceware.org/git/?p=lvm2.git;a=commit;h=cb54d0801d776205788f8f46b31dd9e487833343
commit cb54d0801d776205788f8f46b31dd9e487833343
Author: David Teigland <teigland>
Date: Tue Jan 12 11:53:02 2021 -0600
cachevol: allow forced detaching of damaged or invalid cachevol
A cachevol can be forcibly detached when it's missing devices.
Also allow this if it's damaged/invalid and unrepairable.
This would be needed to recover data from the origin LV after
a cachevol is lost or damaged beyond repair.
Currently in the latest 8.4 rpms, the force doesn't work.
Like mentioned above, it is intended to work in 8.5 with the fix for bug 1915492. We'll wait to try this again once that bug is verified. Otherwise, we can kill the spinning lvconvert cmd for the purposes of testing the 'E' state if this deadlock is not deemed to be a big deal.
Comment 7RHEL Program Management
2022-09-10 07:25:25 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.