Bug 1320730
| Summary: | mirror recovery issues cause filesystems to be shut down | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Heinz Mauelshagen <heinzm> | |
| Component: | lvm2 | Assignee: | LVM and device-mapper development team <lvm-team> | |
| lvm2 sub component: | Mirroring and RAID | QA Contact: | cluster-qe <cluster-qe> | |
| Status: | CLOSED ERRATA | Docs Contact: | ||
| Severity: | high | |||
| Priority: | high | CC: | agk, cmarthal, heinzm, jbrassow, lmiksik, lvm-team, mkolaja, msnitzer, prajnoha, prockai, rbednar, snagar, storage-qe, tlavigne, zkabelac | |
| Version: | 7.3 | Keywords: | Regression, TestBlocker, ZStream | |
| Target Milestone: | rc | |||
| Target Release: | --- | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | lvm2-2.02.152-1.el7 | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, LVM2 failed to handle a failure in mirrors that were not synchronized yet. As a consequence, file systems on top of such mirrors could shut down prematurely. The underlying source code has been modified to fix this bug, and LVM2 now handles mirror repairs correctly. As a result, premature file system shutdowns no longer occur in the described situation.
|
Story Points: | --- | |
| Clone Of: | 1307111 | |||
| : | 1344130 (view as bug list) | Environment: | ||
| Last Closed: | 2016-11-04 04:19:31 UTC | Type: | Bug | |
| 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: | 1090471, 1307111 | |||
| Bug Blocks: | 1344130 | |||
|
Description
Heinz Mauelshagen
2016-03-23 20:54:11 UTC
Bug cloned, because the same issue as in RHEL6 kernel applies to RHEL7 kernel. This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions This bug was not fixed via kernel patch. We provided lvm2 user space regression fix via these two upstream commits: https://www.redhat.com/archives/lvm-devel/2016-April/msg00011.html https://www.redhat.com/archives/lvm-devel/2016-April/msg00012.html this 3rd. commit also fixes possible problem but likely unneeded as it might be impossible to hit with current stacking logic: https://www.redhat.com/archives/lvm-devel/2016-April/msg00013.html This fix makes again automatic mirror recovery working. Without out filesystem may shutdown. (In reply to Zdenek Kabelac from comment #6) > This bug was not fixed via kernel patch. > > We provided lvm2 user space regression fix via these two upstream commits: > > https://www.redhat.com/archives/lvm-devel/2016-April/msg00011.html > https://www.redhat.com/archives/lvm-devel/2016-April/msg00012.html > > this 3rd. commit also fixes possible problem but likely unneeded as it might > be impossible to hit with current stacking logic: > > https://www.redhat.com/archives/lvm-devel/2016-April/msg00013.html > > > This fix makes again automatic mirror recovery working. > Without out filesystem may shutdown. We already have lvm2-2.02.152-1.el7 built which includes these patches which are from lvm2 v2.02.150. So I'm adding this to errata. Verified. Running mirror failure test hundred times passed with both "remove" and "allocate" fault policy. 3.10.0-445.el7.x86_64 lvm2-2.02.156-1.el7 BUILT: Mon Jun 13 10:05:51 CEST 2016 lvm2-libs-2.02.156-1.el7 BUILT: Mon Jun 13 10:05:51 CEST 2016 lvm2-cluster-2.02.156-1.el7 BUILT: Mon Jun 13 10:05:51 CEST 2016 device-mapper-1.02.126-1.el7 BUILT: Mon Jun 13 10:05:51 CEST 2016 device-mapper-libs-1.02.126-1.el7 BUILT: Mon Jun 13 10:05:51 CEST 2016 device-mapper-event-1.02.126-1.el7 BUILT: Mon Jun 13 10:05:51 CEST 2016 device-mapper-event-libs-1.02.126-1.el7 BUILT: Mon Jun 13 10:05:51 CEST 2016 device-mapper-persistent-data-0.6.2-0.1.rc8.el7 BUILT: Wed May 4 09:56:34 CEST 2016 cmirror-2.02.156-1.el7 BUILT: Mon Jun 13 10:05:51 CEST 2016 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-1445.html |