Hello
Everybody,
There is a defect in anaconda, which during partition
creation/deletion, misleads the user with incorrect
information.
I'll try to explain
the defect,
I have a machine
with two hard drives in it as /dev/sda and /dev/sdb
Now during
installation I choose to manually partition the hard drives using "Disk
Druid".
I click
on "New" to create a new partition. I get a new window
where it asks for fstype, mount point et cetera. By default anaconda selects both the hard drives and
creates the partition on any one of them using its own algorithm depending whichever of the hard drive is
less consumed.
Now the
problem,
So during partition
creation, you say "New", only change the fstype to swap and leave the
rest as default. Lets not change the size or
other values and move on with the defaults. The first partiton gets
created on /dev/sda as /dev/sda1
You create another
partition following the same rules. It gets created on /dev/sdb as /dev/sdb1.
You then again go on creating another partition with the same rules and it gets
created on /dev/sda as /dev/sda2.
Good, now comes the problem. Now you select /dev/sdb1 and
click on "Delete". A new pop-up window appears with a
confirmation dialog asking, "Delete partition /dev/sdb1". You Click "Delete".
And bingo, /dev/sda2
gets deleted. Since nothing is written to the disk till now we shouldn't term
it a defect. It's working as designed. But for the sake of eyes it is indeed a
defect. The solution is to add a call which would display "Reordering Partition
Order" or something better you people
suggest, upon each deletion.
The patch attached with this message patches the
partitions.py file in the anaconda source adding a couple of statement in the
sortRequest() function.
The patch attached with
this email simply prints a message whenever (be it during partition creation or
deletion) anaconda uses its own logic to decide on which hard drive to throw the
newly created partition. It won't display any message when you create the first
partition on fresh disks because at that moment anaconda doesn't use its own
logic.
I've checked the patch
and it applies clean to anaconda version 10.1.1.13. It should apply clean to
other versions also.
cd
anaconda-sourcedir/;
patch <
anaconda.patch;
I've checked both RHEL3
and RHEL4. Both releases have the same
problem.
I'd like to hear any
comments or suggestions or a better approach to this
bug.
Regards,
Ritesh Raj
Sarraf
Attachment:
anaconda.patch
Description: anaconda.patch
