Bug 1236690
| Summary: | device failure on exclusively active raid w/ snapshot (on top of cluster VG) leads to deadlock | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jan Kurik <jkurik> |
| Component: | lvm2 | Assignee: | LVM and device-mapper development team <lvm-team> |
| lvm2 sub component: | Mirroring and RAID (RHEL6) | QA Contact: | cluster-qe <cluster-qe> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | high | ||
| Priority: | high | CC: | agk, cluster-qe, cmarthal, heinzm, jbrassow, lvm-team, mjuricek, msnitzer, prajnoha, prockai, salmy, tlavigne, zkabelac |
| Version: | 6.7 | Keywords: | ZStream |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | lvm2-2.02.118-3.el6_7.1 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, if an exclusively activated RAID logical volume with a snapshot was being altered and other LVM commands were simultaneously run, it could cause I/O and LVM commands to hang. This could happen, for example, if 'pvs' was run at the same time as a repair of the RAID logical volume.
The cause was traced to LVM commands attempting to read logical volumes while they were being altered. This issue has been resolved.
|
Story Points: | --- |
| Clone Of: | 1219222 | Environment: | |
| Last Closed: | 2015-07-22 09:40:36 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: | 1219222 | ||
| Bug Blocks: | |||
|
Description
Jan Kurik
2015-06-29 18:03:31 UTC
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-2015-1470.html |