[rhelv6-list] Align partition question on vmware

Thu Mar 20 18:08:20 UTC 2014

>From experience we have seen, Anaconda will correctly handle alignment for partitions done during install. For any additional disks we add, we always manually re-align it.

The issue as I understand it has to do with potentially "double-reading" all blocks.

Kevin

From: rhelv6-list-bounces at redhat.com [mailto:rhelv6-list-bounces at redhat.com] On Behalf Of francis picabia
Sent: Thursday, March 20, 2014 9:59 AM
To: Red Hat Enterprise Linux 6 (Santiago) discussion mailing-list
Subject: [rhelv6-list] Align partition question on vmware

Hi all,
So I install Redhat 6 on a vmware system.  Later I learn
this partition alignment issue common to large 1TB+
drives can be an issue on vmware.

I check a recent system, and the installer seemed
to do the right thing with sda, as the fdisk -lu
reports the first cylinder is 2048

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048    24578047    12288000   83  Linux
I added another vm storage later for /usr/local
and it seems to be set up the old way:

fdisk -lu

Disk /dev/sdb: 219.0 GB, 219043332096 bytes
255 heads, 63 sectors/track, 26630 cylinders, total 427819008 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xaa10a650

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1              63   427810949   213905443+  83  Linux
The guys running a system from there are claiming it is slower than
the Sun 208R they were used to running, and it has no load on it.
Most articles I see about this are taking about the boot loading
disk, while I'm looking at the issue for sdb.  Should I be concerned
and looking at redoing the partitioning?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/rhelv6-list/attachments/20140320/6f86b19c/attachment.htm>