Bug 219414 - Terabyte sized partitions are shown with a "strange" size
Summary: Terabyte sized partitions are shown with a "strange" size
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: anaconda
Version: 5.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Chris Lumens
QA Contact:
URL:
Whiteboard:
: 220384 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-12-12 22:56 UTC by Andreas Thienemann
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-01-09 14:50:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Screenshot showing disk druid (63.10 KB, image/png)
2006-12-12 22:56 UTC, Andreas Thienemann
no flags Details
Showing the problem from comment 3 (74.18 KB, image/png)
2006-12-12 23:11 UTC, Andreas Thienemann
no flags Details

Description Andreas Thienemann 2006-12-12 22:56:18 UTC
During disk druid a partition in a Logical Volume with about 1.2TB is shown as
having a size as 1.21853e+06.

It would be grat, if this size could be shown in a more human readable format.
Especially as the Volume Group is shown as 1220512 MB.

Please see the attached screenshot for an illustration.

Comment 1 Andreas Thienemann 2006-12-12 22:56:18 UTC
Created attachment 143475 [details]
Screenshot showing disk druid

Comment 2 Andreas Thienemann 2006-12-12 23:11:24 UTC
Created attachment 143478 [details]
Showing the problem from comment 3

Comment 3 Andreas Thienemann 2006-12-12 23:15:26 UTC
Furthermore, if one is adding a new LVM partition disk druid is suggesting a
partition size in the e+06 notation.

This size notation is however rejected by the installer.

Comment 4 Chris Lumens 2006-12-22 15:49:21 UTC
*** Bug 220384 has been marked as a duplicate of this bug. ***

Comment 5 Chris Lumens 2007-01-04 20:19:32 UTC
I've modified this in the devel branch.  If we need to get this done in RHEL5 as
well, we'll need to set the appropriate flags.  I don't know if it's too late to
get this in, though.


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