Created attachment 436900 [details] examples of partitioning with logical partitions. Description of problem: Is handling of logical partition by anaconda a bug ? Please see an attached file with examples. Version-Release number of selected component (if applicable): anaconda.i686 13.42-1.fc13 @fedora How reproducible: partitioning a disk with logical partitions. Steps to Reproduce: 1. partition a disk with logical partitions. 2. 3. Actual results: see attachment file. Expected results: see attachment file. Additional info:
Are you seeing an actual error in anaconda when doing installs with logical partitions? Or are you seeing errors attempting to install other operating systems around the partitioning scheme anaconda has created?
Including your attachment as a comment since it is only a small amount of plain text. No need to hide it. Example 1. ========== The last item (Free space) is named "logical" Logical 192425984* 192426569 0 586*Free Space None and at the same is outside of extended partition's range. 4 Primary 105076736* 192425983* 0 87349248*Extended (05) None Should it be called "None" like the Unusable partition between 3 and 2 ? Is that space mapped ("logical") or not ? Will the installer (e.g. anaconda) know about it ? # cfdisk -Ps Partition Table for /dev/sda First Last # Type Sector Sector Offset Length Filesystem Type (ID) Flag -- ------- ----------- ----------- ------ ----------- -------------------- ---- 1 Primary 0 71682029 63 71682030 HPFS/NTFS (07) Boot 3 Primary 71682030 100978904* 0 29296875*Linux (83) None None 100978905* 100980735* 0 1831*Unusable None 2 Primary 100980736* 105076735* 0 4096000*Linux swap / So (82) None 4 Primary 105076736* 192425983* 0 87349248*Extended (05) None 5 Logical 105076736* 192425983* 2048# 87349248*Linux (83) None Logical 192425984* 192426569 0 586*Free Space None # fdisk -l Disk /dev/sda: 98.5 GB, 98522403840 bytes 255 heads, 63 sectors/track, 11978 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xa8a8a8a8 Device Boot Start End Blocks Id System /dev/sda1 * 1 4462 35840983+ 7 HPFS/NTFS /dev/sda2 6286 6541 2048000 82 Linux swap / Solaris /dev/sda3 4463 6286 14648437+ 83 Linux Partition 3 does not end on cylinder boundary. /dev/sda4 6541 11978 43674624 5 Extended /dev/sda5 6541 11978 43673600 83 Linux Partition table entries are not in disk order Example 2. ========== One more "rule to follow" with regard to partitions: http://www.lissot.net/partition/partition-03.html ... Unlike primary partitions, logical partitions must be contiguous. Each logical partition contains a pointer to the next logical partition, ... Between partitions 2 and 4 there is a free space marked as "logical". Logical 219463964* 219463964 0 1*Free Space None It is clearly outside of the Extended partition range. How comes it is called "logical" if it violates the rule of contiguousness ? # cfdisk -Ps Partition Table for /dev/sda First Last # Type Sector Sector Offset Length Filesystem Type (ID) Flag -- ------- ----------- ----------- ------ ----------- -------------------- ---- 1 Primary 0 128519 63 128520 Dell Utility (DE) None 2 Primary 128520 219463963* 0 219335444*HPFS/NTFS (07) Boot Logical 219463964* 219463964 0 1*Free Space None 4 Primary 219463965 615401954 0 395937990 W95 Ext'd (LBA) (0F) None 5 Logical 219463965 223672994 63 4209030 Linux swap / So (82) None 6 Logical 223672995 265618709 63 41945715 Linux (83) Boot 7 Logical 265618710 615401954 63 349783245 Linux (83) None 3 Primary 615401955 625137344 0 9735390 CP/M / CTOS / . (DB) None # fdisk -l Disk /dev/sda: 320.1 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0xe686f016 Device Boot Start End Blocks Id System /dev/sda1 1 8 64228+ de Dell Utility /dev/sda2 * 9 13661 109667722 7 HPFS/NTFS /dev/sda3 38308 38913 4867695 db CP/M / CTOS / ... /dev/sda4 13662 38307 197968995 f W95 Ext'd (LBA) /dev/sda5 13662 13923 2104483+ 82 Linux swap / Solaris /dev/sda6 * 13924 16534 20972826 83 Linux /dev/sda7 16535 38307 174891591 83 Linux
(In reply to comment #2) > Example 1. > ========== > The last item (Free space) is named "logical" "logical" is not a name. It is the type of the partition, which can be primary, logical, or perhaps "none". > > Logical 192425984* 192426569 0 586*Free Space > None > > and at the same is outside of extended partition's range. > > 4 Primary 105076736* 192425983* 0 87349248*Extended (05) > None > > Should it be called "None" like the Unusable partition between 3 and 2 ? This is a question about the cfdisk tool's output. It has nothing to do with anaconda. Different tools may show it as two separate free regions: one inside the extended partition and one (only around 600 sectors) outside the extended partition. Are these partitions that were created by anaconda? I expect they are not. > Is that space mapped ("logical") or not ? The portion of it that lies within the extended partition is logical. The rest is probably not. > Will the installer (e.g. anaconda) know about it ? Why don't you boot the installer and find out? Anaconda uses parted, not fdisk, to read and modify partition tables, so fdisk's view of things isn't important to us. cfdisk's, even less so. > Between partitions 2 and 4 there is a free space marked as "logical". > > Logical 219463964* 219463964 0 1*Free Space > None > > It is clearly outside of the Extended partition range. > How comes it is called "logical" if it violates the rule of contiguousness ? Again, this is a question about cfdisk -- not anaconda.
(In reply to comment #3) > (In reply to comment #2) Hi, yes indeed, this is a cfdisk's view. It does not have any impact on other partitioning tool's workings. Thanks for your comments. The Bug# can be closed. JB