Bug 453813 - installer plays with partition ordering
installer plays with partition ordering
Status: CLOSED DUPLICATE of bug 410011
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-07-02 14:10 EDT by David Woodhouse
Modified: 2008-08-06 15:35 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-08-06 15:35:38 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
screen shot (63.87 KB, image/png)
2008-07-02 14:15 EDT, David Woodhouse
no flags Details

  None (edit)
Description David Woodhouse 2008-07-02 14:10:27 EDT
I'm trying to set up a couple of disks in RAID1, each with a set of partitions.

I tried the 'clone disk' option, but the partitions on sdb ended up in a
_different_ order to those on sda.

I cloned it again to sdc, since I happened to have a third matching disk. That
seemed OK -- at least sdb matched sdc. But I'd forgotten to add a swap
partition. And now I've added swap, all three disks are different.

It would be useful if the installer gave us the option of _numbering_ partitions
as we want them. But getting them in the same order on each disk, when the set
of partitions is identical, would be nice. Getting three _different_ answers for
the same set of partitions is particularly impressive :)

I have four partitions on each disk, and I want them all to be primary
partitions. I'm a little surprised that it defaults to using an extended
partition when there are only four. When I edit a partition and select 'force to
be a primary partition', the installer seems to _forget_ that the partition in
question was already restricted to a certain disk, which I had set earlier while
trying to sort it out.
Comment 1 David Woodhouse 2008-07-02 14:15:02 EDT
Created attachment 310835 [details]
screen shot
Comment 2 David Woodhouse 2008-07-02 15:11:13 EDT
And now it's doing a RAID resync on the whole terabyte. While sitting at the
'install finished. you can reboot now' screen. Is that just a limitation of RAID?
Comment 3 Chris Lumens 2008-08-06 15:35:38 EDT

*** This bug has been marked as a duplicate of bug 410011 ***

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