Bugzilla – Bug 147620
YaST partitioner creates two partitions namend '/dev/hda8'
Last modified: 2006-02-02 15:42:32 UTC
I have the following partition layout: # fdisk -l Disk /dev/hda: 122.9 GB, 122942324736 bytes 255 heads, 63 sectors/track, 14946 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 1 96 771088+ 82 Linux swap / Solaris /dev/hda2 97 1402 10490445 83 Linux /dev/hda3 * 1403 5318 31455270 83 Linux /dev/hda4 5319 14946 77336910 f W95 Ext'd (LBA) /dev/hda5 5319 7929 20972826 83 Linux /dev/hda6 7930 9888 15735636 83 Linux /dev/hda7 9889 11847 15735636 83 Linux /dev/hda8 11848 13806 15735636 83 Linux /dev/hda9 13807 14946 9157018+ 83 Linux # In 'Installation Settings' click on 'Partitioning'. Then select 'Create Custom Partition Setup' Then select '1: 1. IDE, 114.4 GB, /dev/hda...' Then check '6: 15.0 GB ... hda7' and '7: 15.0 GB ... hda8' Back in the 'Installation settings', the following is shown: Partitioning: Delete partition /dev/hda7 (15.0 GB) Delete partition /dev/hda8 (15.0 GB) Create partition /dev/hda8 (19.6 GB) for home with reiserfs Create partition /dev/hda8 (10.0 GB) Note that /dev/hda8 appears twice. The expert partitioner then shows hda8 19.6 GB, hda8 10.0 GB, hda7 8.7 GB. This does not happen when I select hda8 and hda9 instead of hda7 and hda8 above.
Created attachment 66184 [details] y2log after the above procedure
This was indeed a nasty bug hidden deep in libstorage code. It was hidden there since libstorage exists. Before 10.1 it was only possible to remove partitions starting from the highest partition number. I changed this in 10.1 to allow arbitrary removal, so this bug could now more easily be triggered. Will be fixed in beta#4.