Bug 1286737
| Summary: | Resize of full thin-pool loses data | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Jan Kurik <jkurik> |
| Component: | lvm2 | Assignee: | LVM and device-mapper development team <lvm-team> |
| lvm2 sub component: | Thin Provisioning | QA Contact: | cluster-qe <cluster-qe> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | high | ||
| Priority: | high | CC: | agk, cmarthal, dhoward, heinzm, jbrassow, jkurik, lmiksik, mjuricek, msnitzer, pbokoc, prajnoha, prockai, slevine, thornber, zkabelac |
| Version: | 7.2 | Keywords: | ZStream |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | lvm2-2.02.130-5.el7_2.1 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, if an LVM thin pool was filled to capacity while new data was still being written, it was possible to lose some write operations even if the thin pool was being extended at the same time. In some cases, the extended thin pool still could not fit all data waiting to be written, but lvm2 still performed a flush operation, discarding part of the data waiting to be written without logging an error. With this update, lvm2 no longer flushes data when extending thin pools, and data loss is prevented.
|
Story Points: | --- |
| Clone Of: | 1274676 | Environment: | |
| Last Closed: | 2016-02-16 10:40:02 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: | 1274676 | ||
| Bug Blocks: | |||
|
Description
Jan Kurik
2015-11-30 15:59:36 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-2016-0179.html |