Bug 773312
Summary: | up converting an inactive mirror with insufficient devs results in an over concerned warning | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Corey Marthaler <cmarthal> | |
Component: | lvm2 | Assignee: | Jonathan Earl Brassow <jbrassow> | |
Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> | |
Severity: | low | Docs Contact: | ||
Priority: | low | |||
Version: | 5.8 | CC: | agk, dwysocha, heinzm, jbrassow, nperic, prajnoha, prockai, slevine, thornber, zkabelac | |
Target Milestone: | rc | |||
Target Release: | --- | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | lvm2-2.02.88-11.el5 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 848599 (view as bug list) | Environment: | ||
Last Closed: | 2013-10-01 00:27:16 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: | ||||
Bug Blocks: | 807971, 848599, 928849 |
Description
Corey Marthaler
2012-01-11 13:47:31 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release. The same error is still present in the newest lvm for 5.9 The device /dev/sdc1 is already present in the synchornized but inactive mirror. (09:09:31) [root@r5-node01:~]$ lvchange -an insufficient/inactive (09:09:39) [root@r5-node01:~]$ lvconvert -m+1 insufficient/inactive /dev/sdc1 Insufficient suitable allocatable extents for logical volume : 125 more required Unable to allocate extents for mirror(s). ABORTING: Failed to remove temporary mirror layer inactive_mimagetmp_3. Manual cleanup with vgcfgrestore and dmsetup may be required. lvm2-cluster-2.02.88-9.el5 lvm2-2.02.88-9.el5 Fixed by the following upstream commit (which applies cleanly to 2.02.88 release): commit cbcbb677313aa8a4116bcfd13ceccef05fb1f9a9 Author: Jonathan Brassow <jbrassow> Date: Wed Apr 10 16:47:04 2013 -0500 mirror: Fix overly-concerning warning on mirror up-convert failure. Attempting to up-convert an inactive mirror when there is insufficient space leads to the following message: Unable to allocate extents for mirror(s). ABORTING: Failed to remove temporary mirror layer inactive_mimagetmp_3. Manual cleanup with vgcfgrestore and dmsetup may be required. This is caused by a failure to execute the 'deactivate_lv' function in the error condition. The deactivate returns an error because the LV is already inactive. This patch checks if the LV is activate and calls deactivate_lv only if it is. This allows the error cleanup code to work properly in this condition. It wasn't that big of a deal anyway, since there was no previous vg_commit that needed to be reverted. IOW, no harm was done if the allocation failed. The message was scary and useless. UNIT TEST: [root@bp-01 lvm2]# vgs vg VG #PV #LV #SN Attr VSize VFree vg 7 2 0 wz--n- 5.72t 5.71t [root@bp-01 lvm2]# lvs --segments vg LV VG Attr #Str Type SSize lv vg rwi-a-r-- 2 raid1 1.00g mirror vg mwi---m-- 7 mirror 500.00m [root@bp-01 lvm2]# lvconvert -m +1 vg/mirror Insufficient suitable allocatable extents for logical volume : 125 more required Unable to allocate extents for mirror(s). The warning is downscaled in the new package: (04:26:33) [root@r5-node02:~]$ lvconvert -m+1 mirror/insufficient_inactive_upconvert /dev/sdc1 Insufficient suitable allocatable extents for logical volume : 125 more required Unable to allocate extents for mirror(s). (the scenario mention in the OP is passing without issues). Tested on lvm version: lvm2-2.02.88-11.el5 Marking verified with: lvm2-2.02.88-11.el5 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-1352.html |