Bug 587442 - LVMError: lvcreate failed for vg_alma_fast/lv_home: 18:06:18,834 ERROR : Insufficient free extents (748) in volume group vg_alma_fast: 749 required
Summary: LVMError: lvcreate failed for vg_alma_fast/lv_home: 18:06:18,834 ERROR : ...
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.0
Hardware: i386
OS: Linux
Target Milestone: rc
: ---
Assignee: Brian Lane
QA Contact: Release Test Team
Whiteboard: anaconda_trace_hash:a3346164c6cf4ee1e...
: 591941 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2010-04-29 22:33 UTC by Brian Lane
Modified: 2010-07-02 20:48 UTC (History)
1 user (show)

Fixed In Version: anaconda-13.21.50-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-07-02 20:48:06 UTC
Target Upstream Version:

Attachments (Terms of Use)
Attached traceback automatically from anaconda. (5.72 MB, text/plain)
2010-04-29 22:33 UTC, Brian Lane
no flags Details
anaconda traceback from failure reproducer (954.08 KB, text/plain)
2010-05-14 18:03 UTC, Brian Lane
no flags Details
Extra debugging (355.57 KB, text/plain)
2010-05-27 16:18 UTC, Brian Lane
no flags Details

Description Brian Lane 2010-04-29 22:33:50 UTC
The following was filed automatically by anaconda:
anaconda 13.21.32 exception report
Traceback (most recent call first):
  File "/usr/lib/anaconda/storage/devicelibs/lvm.py", line 374, in lvcreate
    raise LVMError("lvcreate failed for %s/%s: %s" % (vg_name, lv_name, msg))
  File "/usr/lib/anaconda/storage/devices.py", line 2353, in create
    lvm.lvcreate(self.vg.name, self._name, self.size, progress=w)
  File "/usr/lib/anaconda/storage/deviceaction.py", line 203, in execute
  File "/usr/lib/anaconda/storage/devicetree.py", line 693, in processActions
  File "/usr/lib/anaconda/storage/__init__.py", line 282, in doIt
  File "/usr/lib/anaconda/packages.py", line 109, in turnOnFilesystems
  File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep
    rc = stepFunc(self.anaconda)
  File "/usr/lib/anaconda/dispatch.py", line 126, in gotoNext
  File "/usr/lib/anaconda/gui.py", line 1258, in nextClicked
LVMError: lvcreate failed for vg_alma_fast/lv_home: 18:06:18,834 ERROR   :   Insufficient free extents (748) in volume group vg_alma_fast: 749 required

Comment 1 Brian Lane 2010-04-29 22:33:58 UTC
Created attachment 410254 [details]
Attached traceback automatically from anaconda.

Comment 3 RHEL Program Management 2010-04-29 23:32:54 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for

Comment 4 David Cantrell 2010-05-01 02:24:44 UTC

How did you perform the installation?

Comment 5 Brian Lane 2010-05-03 15:47:52 UTC
I was trying to confirm a bugfix (can't find the bug number right now) that was using a RAID5 and a RAID0 so I setup the virtual with 8 1G drives. I'm not sure if I can reproduce this, but it looks like a rounding error when calculating extents.

Comment 6 Brian Lane 2010-05-03 21:23:05 UTC
I was working on bug 585839, I just tried to reproduce this and couldn't.

Comment 7 David Cantrell 2010-05-07 04:44:51 UTC
Moving to MODIFIED per commit #6.

Comment 10 Alexander Todorov 2010-05-13 12:03:33 UTC
With RHEL6.0-20100511.3:

I've installed using the steps to reproduce from https://bugzilla.redhat.com/show_bug.cgi?id=585839#c0 (the bug Brian was testing) (virtual system, 4 disks, same partitioning but with smaller disk sizes) and install completed successfully. Wrt comment #6 I'll close this.

Comment 11 Alexander Todorov 2010-05-13 14:21:57 UTC
*** Bug 591941 has been marked as a duplicate of this bug. ***

Comment 12 Alexander Todorov 2010-05-13 14:26:33 UTC
I've hit this with 0512.0 tree with slightly different setup. I didn't leave any freespace at the beginning nor created other partitions than the RAID ones.

My setup is a KVM domU with 4 disks (10GB each) with the below layout. Because those disks were used in previous installs after starting stage2 I've switched to tt2 and did `dd if=/dev/zero of=/dev/vdX bs=1M count=10` for each disk and let anaconda re-initialize all disks. Manually created this layout in anaconda.

vda1  200MB  /boot ext4
vda2 4000MB  software raid
vda3 4000MB  software raid
vda4 - Extended
vda5 - all available space, swap

vdb1 4000MB  software raid
vdb2 4000MB  software raid
Free space

vdc1 4000MB  software raid
vdc2 4000MB  software raid
Free space

vdc1 4000MB  software raid
vdc2 4000MB  software raid
Free space

md0, RAID 5 (vda2, vdb2, vdc2, vdd2), 3 active, 1 spare, PV
md1, RAID 0 (vda3, vdb1, vdc1, vdd1), 4 active, 0 spare, PV

vg_safe on md0 with lv_root, / - all space, ext4
vg_fast on md1 with lv_home - all space, ext4


Comment 13 Brian Lane 2010-05-14 18:03:37 UTC
Created attachment 414125 [details]
anaconda traceback from failure reproducer

Comment 14 Brian Lane 2010-05-24 18:40:22 UTC
A somewhat simpler way to recreate this:

vda1 500M /boot
vda2 4000M SW RAID

vdb1 500M swap
vdb2 4000M SW RAID

vdc1 4000M SW RAID

vdd1 4000M SW RAID

md0, RAID5 (vda2, vdb2, vdc1, vdd1) 4 active, 0 spares

vg_safe on md0 with all space

md0's size is 11999 and the vg_safe size is 11996

Comment 15 Brian Lane 2010-05-27 16:18:50 UTC
Created attachment 417297 [details]
Extra debugging

Added logging of PV size before and after creation. Search for 'size ==' to find the entries.

Comment 16 Brian Lane 2010-06-01 16:36:46 UTC
Committed 7a9698b3cd93bf4f6d297b7bccf6f463aebe34e8 and 4a76ede46f1c8a5bb02a3055e186f4134d18342a to fix this. Solution was to adjust the estimated size of the superblocks to match mdadm's usage of v1.1 metadata in the RAID.

Comment 18 Alexander Todorov 2010-06-25 10:58:49 UTC
tested with anaconda-13.21.50-9. (0622.1 build) and the partitioning scheme from comment #12. There was no traceback. Moving to VERIFIED.

Comment 19 releng-rhel@redhat.com 2010-07-02 20:48:06 UTC
Red Hat Enterprise Linux Beta 2 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

Note You need to log in before you can comment on or make changes to this bug.