Bug 607316
Summary: | primary log device removal after failure does not work | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Corey Marthaler <cmarthal> |
Component: | lvm2 | Assignee: | Petr Rockai <prockai> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Corey Marthaler <cmarthal> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.0 | CC: | agk, antillon.maurizio, coughlan, ddumas, dwysocha, heinzm, jbrassow, joe.thornber, mbroz, prajnoha, prockai, syeghiay |
Target Milestone: | rc | Keywords: | TestBlocker |
Target Release: | --- | Flags: | cmarthal:
needinfo+
|
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | lvm2-2.02.72-7.el6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-11-10 21:08:10 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 606931 | ||
Bug Blocks: |
Description
Corey Marthaler
2010-06-23 19:22:57 UTC
For all I can tell, this is due to incomplete support for mirrored log in lvconvert --repair. I am working on it. I take that back, I have noticed this: Jun 23 18:59:02 taft-01 lvm[1950]: LV helter_skelter/syncd_primary_log_2legs_2logs_1_mlog_mimage_0 in use: not deactivating this looks related to bug 606931. Let's mark this as a dependency -- when 606931 is fixed we should see whether this got fixed as well, or there is an additional issue specific to mirrored logs. Relevant patch checked in upstream. Is this fix in the latest build (lvm2-2.02.72-7.el6.x86_64)? If so, a new log device is not allocated, instead the mirror is down convert to a linear. Is this what's expected? Hmm. Do you mean that the whole mirror is downconverted, or just that the mirrored log is downconverted to linear? If the former happens, that is certainly surprising, since the fallback policy on that scenario is to use core log which should certainly not fail if both (toplevel) mirror legs are healthy. On the other hand, if it is the mirrored log that ends up linear, then that may be unintentional but is probably not a serious problem (we can fix this in 6.1 in that case). Certainly detailed output would help in any case to clarify what's going on. Thanks. It's the mirrored log that ends up a linear. image0 sdb image1 sdc log image0 sdd log image1 sde if you fail sdd and your fault policy is allocate, the mirror will end up looking like this: image0 sdb image1 sdc log sde Jon explained to me that this is expected (at least for the time being) since there is no way to go from disk to mirrored log with the current code. The original issue in this bug is fixed. The issue mentioned in comment #7 is documented in bug 607334. Marking verified in the latest rpms. 2.6.32-59.1.el6.x86_64 lvm2-2.02.72-8.el6 BUILT: Wed Aug 18 10:41:52 CDT 2010 lvm2-libs-2.02.72-8.el6 BUILT: Wed Aug 18 10:41:52 CDT 2010 lvm2-cluster-2.02.72-8.el6 BUILT: Wed Aug 18 10:41:52 CDT 2010 udev-147-2.22.el6 BUILT: Fri Jul 23 07:21:33 CDT 2010 device-mapper-1.02.53-8.el6 BUILT: Wed Aug 18 10:41:52 CDT 2010 device-mapper-libs-1.02.53-8.el6 BUILT: Wed Aug 18 10:41:52 CDT 2010 device-mapper-event-1.02.53-8.el6 BUILT: Wed Aug 18 10:41:52 CDT 2010 device-mapper-event-libs-1.02.53-8.el6 BUILT: Wed Aug 18 10:41:52 CDT 2010 cmirror-2.02.72-8.el6 BUILT: Wed Aug 18 10:41:52 CDT 2010 Red Hat Enterprise Linux 6.0 is now available and should resolve the problem described in this bug report. This report is therefore being closed with a resolution of CURRENTRELEASE. You may reopen this bug report if the solution does not work for you. |