Bug 832392
| Summary: | pvmove cannot be used with lvm.conf option issue_discards | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Zdenek Kabelac <zkabelac> |
| Component: | lvm2 | Assignee: | Zdenek Kabelac <zkabelac> |
| Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 6.3 | CC: | agk, cmarthal, coughlan, dwysocha, heinzm, jbrassow, mbroz, msnitzer, nperic, prajnoha, prockai, thornber, zkabelac |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | lvm2-2.02.97-2.el6 | Doc Type: | Bug Fix |
| Doc Text: |
Without this fix, when issue_discards=1 is configured in the /etc/lvm/lvm.conf file, moving physical volumes via the pvmove command results in data loss.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-02-21 08:10:41 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: | |||
| Bug Blocks: | 852438 | ||
|
Description
Zdenek Kabelac
2012-06-15 10:07:58 UTC
This is critical bug btw, it means that you will lose your data completely if using pvmove with issue_discards=1. Original report from lvm-devel list: https://www.redhat.com/archives/lvm-devel/2012-June/msg00025.html Note that issue_discards is NOT enabled by default. So this only affects people who explicitly turned it on.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
When issue_discards=1 is configured in the /etc/lvm/lvm.conf file, moving physical volumes via the pvmove command results in data loss. To work around this issue, ensure that issue_discards=0 is set in your lvm.conf file before moving any physical volumes.
Discards are issued when releasing a PV segment. But this code is used both when deleting the space AND when moving it elsewhere. (Need to check whether or not some lvconvert code paths are affected too.) The code was added in 2.02.85, so RHEL6.2 might be affected too. Proposed fix: https://lists.fedorahosted.org/pipermail/lvm2-commits/2012-June/000037.html https://lists.fedorahosted.org/pipermail/lvm2-commits/2012-June/000038.html https://lists.fedorahosted.org/pipermail/lvm2-commits/2012-June/000039.html Adding QA ack for 6.4. Devel will need to provide unit testing results however before this bug can be ultimately verified by QA. If I understand correctly, if this patch goes in, then the current Technical Note
("...issue_discards=1...results in data loss...ensure that issue_discards=0 is set in your lvm.conf file before moving any physical volumes.")
is not needed in 6.4.
It is needed in earlier releases. (Should we propose the fix for 6.3.z?)
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1 +1 @@
-When issue_discards=1 is configured in the /etc/lvm/lvm.conf file, moving physical volumes via the pvmove command results in data loss. To work around this issue, ensure that issue_discards=0 is set in your lvm.conf file before moving any physical volumes.+Without this fix, when issue_discards=1 is configured in the /etc/lvm/lvm.conf file, moving physical volumes via the pvmove command results in data loss.
Moving to Verified (SanityOnly). All single machine pvmove regression tests passed. kernel-2.6.32-330.el6.x86_64 lvm2-2.02.98-2.el6.x86_64 device-mapper-1.02.77-2.el6.x86_64 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. http://rhn.redhat.com/errata/RHBA-2013-0501.html |