Bug 84481 - initial size of pre-existing logical volume group has wrong unit
Summary: initial size of pre-existing logical volume group has wrong unit
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 9
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2003-02-17 21:49 UTC by Alexandre Oliva
Modified: 2007-04-18 16:51 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2003-05-11 20:20:05 UTC

Attachments (Terms of Use)

Description Alexandre Oliva 2003-02-17 21:49:34 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030120

Description of problem:
When a line such as `volgroup <name> --noformat'  is present in a kickstart
file, the size of the volume group is computed in Kb, but the disk druid screen
claims it's in Mb.  
The vt3 line `used size vs. available for vg <name>'  has the total (and not
available) size in the wrong unit as well.

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

How reproducible:

Steps to Reproduce:
1.Create a kickstart file that preserves a pre-existing volume group
2.Start the installer with it

Actual Results:  When you get to disk druid, before you click on any of the
logical volume partitions, the displayed size is in Kb, not Mb.

Expected Results:  It should be in MB, as said in the title of the column.

Additional info:

Comment 1 Jeremy Katz 2003-02-20 07:16:15 UTC
Also true for non kickstart.  Fixed in CVS

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