Bug 754598

Summary: core to disk log conversion fails: Internal error: _alloc_parallel_area called without any allocation to do
Product: Red Hat Enterprise Linux 5 Reporter: Corey Marthaler <cmarthal>
Component: lvm2Assignee: Jonathan Earl Brassow <jbrassow>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: high Docs Contact:
Priority: high    
Version: 5.8CC: agk, dwysocha, heinzm, jbrassow, mbroz, prajnoha, prockai, thornber, zkabelac
Target Milestone: rcKeywords: Regression, TestBlocker
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: lvm2-2.02.88-5.el5 Doc Type: Bug Fix
Doc Text:
Do not document (bug in unreleased version).
Story Points: ---
Clone Of: 738832 Environment:
Last Closed: 2012-02-21 06:05:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 738832    
Bug Blocks: 743047, 758797    
Attachments:
Description Flags
RHEL5.8 port of upstream patch none

Comment 1 Corey Marthaler 2011-11-16 22:48:25 UTC
This exists in the latest 5.8 rpms.

2.6.18-274.el5
lvm2-2.02.88-4.el5    BUILT: Wed Nov 16 09:40:55 CST 2011
lvm2-cluster-2.02.88-4.el5    BUILT: Wed Nov 16 09:46:51 CST 2011
device-mapper-1.02.67-2.el5    BUILT: Mon Oct 17 08:31:56 CDT 2011
device-mapper-event-1.02.67-2.el5    BUILT: Mon Oct 17 08:31:56 CDT 2011
cmirror-1.1.39-10.el5    BUILT: Wed Sep  8 16:32:05 CDT 2010
kmod-cmirror-0.1.22-3.el5    BUILT: Tue Dec 22 13:39:47 CST 2009


SCENARIO - [looping_mirror_log_converts]
Create a core log mirror and then convert it's log from core to disk to mirrored 20 times
grant-01: lvcreate -m 1 -n mirror_log_convert --mirrorlog core -l 11508 mirror_sanity /dev/sdb1 /dev/sdb2 /dev/sdb3 /dev/sdb6

Convert loop 1
Convert to disk log
grant-01: lvconvert -m 1 --mirrorlog disk /dev/mirror_sanity/mirror_log_convert
  Internal error: _alloc_parallel_area called without any allocation to do.
  Internal error: _alloc_parallel_area called without any allocation to do.
  Internal error: _alloc_parallel_area called without any allocation to do.
  Insufficient suitable allocatable extents for logical volume : 0 more required
  Unable to allocate extents for mirror log.
converting to disk log failed

Comment 2 Jonathan Earl Brassow 2011-11-22 21:26:26 UTC
Created attachment 535199 [details]
RHEL5.8 port of upstream patch

Comment 3 Milan Broz 2011-12-02 23:00:47 UTC
Fixed in lvm2-2.02.88-5.el5.

Comment 6 Corey Marthaler 2011-12-05 21:07:40 UTC
Fix verified in the latest rpms.

2.6.18-274.el5

lvm2-2.02.88-5.el5    BUILT: Fri Dec  2 12:25:45 CST 2011
lvm2-cluster-2.02.88-5.el5    BUILT: Fri Dec  2 12:48:37 CST 2011
device-mapper-1.02.67-2.el5    BUILT: Mon Oct 17 08:31:56 CDT 2011
device-mapper-event-1.02.67-2.el5    BUILT: Mon Oct 17 08:31:56 CDT 2011
cmirror-1.1.39-10.el5    BUILT: Wed Sep  8 16:32:05 CDT 2010
kmod-cmirror-0.1.22-3.el5    BUILT: Tue Dec 22 13:39:47 CST 2009


SCENARIO - [looping_mirror_log_converts]
Create a core log mirror and then convert it's log from core to disk to mirrored 20 times
taft-02: lvcreate -m 1 -n mirror_log_convert --mirrorlog core -l 19101 mirror_sanity /dev/sdh1 /dev/sdh2 /dev/sdg1 /dev/sdg2
Skipping redundant logged cmirrors are not supported

Convert loop 1
Convert to disk log
taft-02: lvconvert -m 1 --mirrorlog disk /dev/mirror_sanity/mirror_log_convert
Verifying that mirror redundancy isn't lost
Convert back to core log

Convert loop 2
Convert to disk log
taft-02: lvconvert -m 1 --mirrorlog disk /dev/mirror_sanity/mirror_log_convert
Verifying that mirror redundancy isn't lost
Convert back to core log
[...]

Comment 7 Milan Broz 2011-12-06 23:35:39 UTC
    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:
Do not document (bug in unreleased version).

Comment 8 errata-xmlrpc 2012-02-21 06:05:43 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.

http://rhn.redhat.com/errata/RHBA-2012-0161.html