On 03/21/2012 02:18 PM, David Lehman wrote: >> start: 63551 end: 64259 length: 709 >> > This free region is at the beginning of the extended partition. The >> > extended partition starts at sector 63488 and the first logical >> > partition starts at 67584. >> > -> Why there is a free space at all? I did not request any. >> > -> What are 3325 sectors between the free space end and the first >> > logical partition start? I know, there is one sector for logical >> > partition metadata, but 1.6MB, which is not part of any partition nor >> > free space region, seems too much to me. >> > -> Similarly, what are 63 sectors between the extended partition start >> > and the free space start? 1 sector is for logical partition metadata, >> > but the rest? > > We are somewhat more liberal with rounding start sector up for logical > partitions, basically because parted is more aggressive in aligning > start of logical partitions than it is with normal partitions. Also, we > need to account for at least one sector of metadata before each logical > partition. In some unfortunate cases this bump to the next MB boundary > can amount to 2047 520-byte sectors. Again, parted is so aggressive with > this that we had to do the same in order to ensure that parted > magic/fixups do not cause unwanted surprises when the partitions are > added to disk. > Ok, I understand the free space *between* logical partitions. But the above is the first logical partition. Looking at the raw partition data (obtained by cfdisk), I can see that the first logical partition metadata are at sector 63488, i.e. the first sector of the extended partition. The real partition data starts at sector 67584, which is 2 megabytes (!) after the metadata. I would expect just 1 megabyte between, for the alignment. But that's something I can live with. What troubles me much more is that pyanaconda.storage.partitioning.getFreeRegions() reports a free region in these 2 megabytes between logical partition metadata and real partition data! IMHO nothing should be allowed there! fdisk output: /dev/sdb1 2048 22527 10240 83 Linux /dev/sdb2 22528 43007 10240 83 Linux /dev/sdb3 43008 63487 10240 83 Linux /dev/sdb4 63488 2097151 1016832 5 Extended /dev/sdb5 67584 88063 10240 83 Linux ... cfdisk output: # Type Sector Sector Offset Length ... 1 Primary 2048* 22527* 0 20480* 2 Primary 22528* 43007* 0 20480* 3 Primary 43008* 63487* 0 20480* 4 Primary 63488* 2097151* 0 2033664*Extended 5 Logical 63488* 88063* 4096# 24576 6 Logical 88064* 110591* 2048# 22528 ... Offset is the distance between metadata and partition data - fdisk shows only the real partition data, usable by /dev/sda5 block device. Jan _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
