Bug 140355

Summary:	Order of KB/MB/GB/Extents during LV creation
Product:	Red Hat Enterprise Linux 4	Reporter:	Derek Anderson <danderso>
Component:	system-config-lvm	Assignee:	Jim Parsons <jparsons>
Status:	CLOSED RAWHIDE	QA Contact:	Jim Parsons <jparsons>
Severity:	low	Docs Contact:
Priority:	medium
Version:	4.0	CC:	cluster-maint, danderso
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-11-23 19:28:59 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Derek Anderson 2004-11-22 16:12:08 UTC

Description of problem:
A picky little bug.  In the LV creation dialog the order goes from MB
to GB to KB to Extents.  I feel that at least the KB/MB/GB should be
in that order.

Maybe Extents/KB/MB/GB with Extents as default.

Version-Release number of selected component (if applicable):
system-config-lvm-0.9.12-1.0

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Jim Parsons 2004-11-22 23:34:46 UTC

Fixed @ 0.9.14-1.0
I tested this alot, but the more testing the better, please. This is
important functionality.

Comment 2 Derek Anderson 2004-11-23 19:28:59 UTC

Order is now Extent/GB/MB/KB.  That's OK with me.  Functionality of
each is also working correctly for creating LVs.

Verified in version system-config-lvm-0.9.17-1.0.