Created attachment 335715 [details] screenshot: Partition 1 does not end on cylinder boundary Description of problem: problem with partition layout (screenshot attached) Version-Release number of selected component (if applicable): boot.iso from 17.03.2009 anaconda-11.5.0.31-1.i586.rpm How reproducible: Steps to Reproduce: 1. install in a VM via boot.iso 2. 3. Actual results: Expected results: Additional info:
We are aware of the fact that we are not creating partitions on cylinder boundaries at this time. We are interested in determining if it is actually necessary or if it is just something that people do out of some vague fear. If you are seeing any negative consequences, or know of any, please let us know.
Head Scratch up to now my "vague fear" only is that we/you will start to see this or similar bug reports from people are able to do "fdisk" on c-l-i... close this one !
As you wish.
*** Bug 491748 has been marked as a duplicate of this bug. ***
*** Bug 497668 has been marked as a duplicate of this bug. ***
Hi, I have encountered the same problem with RHEL6.2 virtual machine. [root@vmrlnx179-74 ~]# fdisk -l Disk /dev/sda: 17.2 GB, 17179869184 bytes 64 heads, 32 sectors/track, 16384 cylinders Units = cylinders of 2048 * 512 = 1048576 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0005b2b5 Device Boot Start End Blocks Id System /dev/sda1 * 2 201 204800 83 Linux Partition 1 does not end on cylinder boundary. /dev/sda2 202 2249 2097152 82 Linux swap / Solaris Partition 2 does not end on cylinder boundary. /dev/sda3 2250 16384 14474240 83 Linux Partition 3 does not end on cylinder boundary. Disk /dev/sdb: 10.7 GB, 10737418240 bytes 64 heads, 32 sectors/track, 10240 cylinders Units = cylinders of 2048 * 512 = 1048576 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xc0ddf28b Device Boot Start End Blocks Id System
(In reply to comment #6) > Hi, I have encountered the same problem with RHEL6.2 virtual machine. > Please see comment 1.
(In reply to comment #1) > We are aware of the fact that we are not creating partitions on cylinder > boundaries at this time. We are interested in determining if it is actually > necessary or if it is just something that people do out of some vague fear. > If you are seeing any negative consequences, or know of any, please let us > know. Hi, If you are not using cylinder boundaries, what do you use to create partitions ?
(In reply to comment #8) > (In reply to comment #1) > > We are aware of the fact that we are not creating partitions on cylinder > > boundaries at this time. We are interested in determining if it is actually > > necessary or if it is just something that people do out of some vague fear. > > If you are seeing any negative consequences, or know of any, please let us > > know. > > Hi, > > If you are not using cylinder boundaries, what do you > use to create partitions ? We use sectors. We align them according to the alignment data provided by the kernel for each block device.