Bug 836653
Summary: | raid1 mirror reduction finishes "successfully" even though it failed to reduce the legs | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Corey Marthaler <cmarthal> |
Component: | lvm2 | Assignee: | Alasdair Kergon <agk> |
Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.3 | CC: | agk, dwysocha, heinzm, jbrassow, msnitzer, nperic, prajnoha, prockai, slevine, thornber, zkabelac |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | lvm2-2.02.97-2.el6 | Doc Type: | Bug Fix |
Doc Text: |
A failure to reduce the size of a Logical Volume was sometimes not detected and 'lvremove' exited successfully even though it had failed. Errors are now detected and reported.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-02-21 08:11:03 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: | 840699 |
Description
Corey Marthaler
2012-06-29 20:04:53 UTC
This should be considered for 6.3.z. This is fixed in v2.02.97 (http://git.fedorahosted.org/cgit/lvm2.git/commit/?id=a5ddb347e569a953d6732d8d9f72857a560b5bcd): # lvcreate -L 128m -m1 --type raid1 vg Logical volume "lvol0" created # lvreduce -f -L 30M /dev/vg/lvol0 Rounding size to boundary between physical extents: 32.00 MiB WARNING: Reducing active logical volume to 32.00 MiB THIS MAY DESTROY YOUR DATA (filesystem etc.) Reducing logical volume lvol0 to 32.00 MiB Unable to reduce RAID LV - operation not implemented. # echo $? 5 # lvs LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert lvol0 vg rwi-a-m- 128.00m 100.00 Verified with : lvm2-2.02.98-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 |