Bug 115166 - Bad partitionning by anaconda
Summary: Bad partitionning by anaconda
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda   
(Show other bugs)
Version: 1
Hardware: i386 Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
Keywords: FutureFeature
Depends On:
TreeView+ depends on / blocked
Reported: 2004-02-07 14:40 UTC by Jean Francois Martinez
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-02-18 00:30:33 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Jean Francois Martinez 2004-02-07 14:40:12 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20030131

Description of problem:
When I choose to partition MANUALLY through anaconda the end result
respect my wishes for partition sizes but the layout I get is both
different than the one I gave and IMHO grossly suboptimal.

Tracks in the outer ridge (low numbered tracks) have more blocks than
tracks in the inner ridge.  For that reason they are faster and should
be used for the partitions who will see the heaviest use.

But when I partition with anaconda I find the boot partition at the
very first (that is OK since it is an architectural constraint) and
partitions I consider unimportant at the beginng while the important
ones are at the end in the slowest part of the disk. (it seems to use
a kind of LIFO stack)

When user selects to partition manually Anaconda should step aside
since it cannot guess what will be the important partition (/usr for a
developer machine, the one containing the database for an Oracle server) 

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

How reproducible:

Steps to Reproduce:
1. Install any RedHat or Fedora version
2. Choose to partition manually through Disk druid 

Actual Results:  Partitions in LIFO order

Expected Results:  Partitionning accrding to my wishes

Additional info:

Comment 1 Jeremy Katz 2004-02-18 00:30:33 UTC
Partitions are ordered by size (with exceptions) so that growing can
fill the disk in a sane fashion.  If you want more explicit
partitioning, you can choose to edit the free space and set partitions
in explicit cylinder ranges.

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