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.
This needs to be covered by the documentation being produced for bug 1015096. There will be no change to the lvm2 package for this at this stage.
Comment 9Jonathan Earl Brassow
2014-08-19 00:40:36 UTC
To answer the question, it is expected that I/O to any of the thin-pool's thinLVs would fail in this case.
I cannot tell you for sure if corruption would ensue. I suspect that if the metadata device could be brought back, the thin-pool would be usable again and there would be no corruption. You would need to check with the kernel maintainer for sure though.
If the metadata device does not come back, then you have lost all your pointers to where the data is with no good way of recoverying them - a complete loss.
This is why the documentation in 'lvmthin.7' is so emphatic about using RAID (at least) for the metadata device. See the section entitled "Tolerate device failures using raid".
Comment 11Jonathan Earl Brassow
2015-03-03 20:26:15 UTC
(In reply to Jonathan Earl Brassow from comment #9)
> To answer the question, it is expected that I/O to any of the thin-pool's
> thinLVs would fail in this case.
>
> I cannot tell you for sure if corruption would ensue. I suspect that if the
> metadata device could be brought back, the thin-pool would be usable again
> and there would be no corruption. You would need to check with the kernel
> maintainer for sure though.
>
> If the metadata device does not come back, then you have lost all your
> pointers to where the data is with no good way of recoverying them - a
> complete loss.
>
> This is why the documentation in 'lvmthin.7' is so emphatic about using RAID
> (at least) for the metadata device. See the section entitled "Tolerate
> device failures using raid".
Given that the question has been answered, I am closing this as NOTABUG. If more information is needed, you can reopen.