Bug 682276

Summary: DeviceCreateError: ('lvcreate failed for vg_zalem/lv_home: Volume group "vg_zalem" has insufficient free space (624 extents): 13614 required.\n', 'vg_zalem-lv_home')
Product: [Fedora] Fedora Reporter: Sandro Mathys <sandro>
Component: anacondaAssignee: David Lehman <dlehman>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 15CC: anaconda-maint-list, b1038853, carlos_si, charlieb-fedora-bugzilla, dante, denvorhu, jonathan, jstodola, lgpr.parra, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: anaconda_trace_hash:7d31f8335ec3438092029fc4bd55ece7047b99c6e25b841968109ac56c76f4b3
Fixed In Version: anaconda-16.10-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-12 23:04:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda. none

Description Sandro Mathys 2011-03-04 16:56:58 UTC
The following was filed automatically by anaconda:
anaconda 15.20.1 exception report
Traceback (most recent call first):
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 748, in create
    raise DeviceCreateError(str(e), self.name)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/deviceaction.py", line 240, in execute
    self.device.create(intf=intf)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 313, in processActions
    action.execute(intf=self.intf)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 355, in doIt
    self.devicetree.processActions()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/packages.py", line 116, in turnOnFilesystems
    anaconda.storage.doIt()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 211, in moveStep
    rc = stepFunc(self.anaconda)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 130, in gotoNext
    self.moveStep()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1257, in nextClicked
    self.anaconda.dispatch.gotoNext()
DeviceCreateError: ('lvcreate failed for vg_zalem/lv_home:   Volume group "vg_zalem" has insufficient free space (624 extents): 13614 required.\n', 'vg_zalem-lv_home')

Comment 1 Sandro Mathys 2011-03-04 16:57:04 UTC
Created attachment 482328 [details]
Attached traceback automatically from anaconda.

Comment 2 Sandro Mathys 2011-03-04 17:03:40 UTC
Okay, this was fun to produce :)

Steps to reproduce:
- Choose 2 disks (in my case md126 and sdc) as targets
- Choose to review partitioning layout
- Notice that both disks are consumed in VG
- Remove one disk from the VG
- Notice that only one disk is consumed in that VG anymore
- Notice that the volumes within the VG still show the same size as before
- Click the Next button
- Notice that there's no warning
- Click to Write changes to disk
- Exception!

Of course this is nothing a user will normally hit...I only did because I first thought to use sdc as well and when thinking about it I was not completely sure where I might have data left on it so I removed it (as this was only a QA installation anyway).

Comment 3 Jan Stodola 2011-04-11 15:03:05 UTC
Created attachment 491255 [details]
Attached traceback automatically from anaconda.

Comment 4 Leoner Parra 2011-05-01 17:20:40 UTC
Created attachment 496082 [details]
Attached traceback automatically from anaconda.

Comment 5 asdafus 2011-05-26 18:17:57 UTC
Created attachment 501157 [details]
Attached traceback automatically from anaconda.

Comment 6 David Lehman 2011-05-26 18:52:00 UTC
Based on the reproducer in comment 2 this is a regression caused by changes made to accommodate kickstart users who specify growable PVs with useless initial sizes like 1MB (commit 86be5d55ed69e0a0). A patch is in the works...

Comment 7 Eldor 2011-05-29 08:59:30 UTC
Created attachment 501578 [details]
Attached traceback automatically from anaconda.

Comment 8 denvor 2011-06-26 01:46:25 UTC
Created attachment 509942 [details]
Attached traceback automatically from anaconda.

Comment 9 denvor 2011-06-26 02:07:29 UTC
Created attachment 509944 [details]
Attached traceback automatically from anaconda.

Comment 10 Dante 2011-08-12 21:16:17 UTC
Created attachment 518108 [details]
Attached traceback automatically from anaconda.

Comment 11 Dante 2011-08-12 21:24:23 UTC
New installation to an external USB Hard-Drive

Comment 12 David Lehman 2011-08-12 23:04:42 UTC
Fixed in anaconda-16.10-1, meaning the fix will be in Fedora 16's installer.

Comment 13 Charlie Brady 2013-07-08 19:05:51 UTC
(In reply to David Lehman from comment #12)
> Fixed in anaconda-16.10-1, meaning the fix will be in Fedora 16's installer.

Could you provide a link to the commit which includes this fix? bug 895982 might be due to the same root cause.