Bug 138006 - LV creation, use remaining space in GB: rounding error failures
Summary: LV creation, use remaining space in GB: rounding error failures
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: system-config-lvm
Version: 4.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Jim Parsons
QA Contact: Jim Parsons
URL:
Whiteboard:
Depends On:
Blocks: 135876
TreeView+ depends on / blocked
 
Reported: 2004-11-03 19:43 UTC by Derek Anderson
Modified: 2009-04-16 23:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-11-12 16:37:28 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Derek Anderson 2004-11-03 19:43:31 UTC
Description of problem:
Create a VG and then create a new LV on it.  Change type dropdown to
"Gigabytes" and click "Use Remaining Space".  Give it a Name and click
"OK".

Result on the command line:
  Insufficient free extents (92782) in volume group VG1: 92783 required


Version-Release number of selected component (if applicable):


How reproducible:
Depending on the size of your VG, %100.  You may get lucky and the
rounding will not cause a problem.

Steps to Reproduce:
1.  Create LV on VG
2.  Use Remaining Space in Gigabytes
3.
  
Actual results:
LV not created, "Insufficient free extents (17151) in volume group
VG2: 17152 required"

Expected results:
LV created.

Additional info:

Comment 1 Jim Parsons 2004-11-11 23:22:43 UTC
This is fixed in the upcoming 0.9.9-1.0 build. Now if the user wishes
to  use all remaining space on the VG for a new LV, clicking the 'use
remaining space' button stores the extents available, and passes the
discrete number of extents left to the lvcreate command. Yes, the case
where a user clicks the button, then edits the Size field before
clicking OK is covered! :-)

Comment 2 Derek Anderson 2004-11-12 16:37:28 UTC
Verified in system-config-lvm-0.9.9-1.0.


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