VMware Solutions Discussions

VM OS disk alignment, should it be 32 or 64

daniel_kaiser
3,934 Views

What's the correct disk alignment setting for a guest machine running Windows 2003.  TR-3749 version 2 page 95 states "create partition primary align=32, but MS states that it should be 64 unless otherwise.  So can someone confirm the correct alignment settings for a partition that's used in Windows 2003 (200GB+ partition).  Should it be 32 or 64?

Thanks.

Dan

1 ACCEPTED SOLUTION

chrisgeb
3,934 Views

I would say that either would work just fine however lets consider the standardization of alignment for the cloud.  Some vendors recommend different sizes based on their own filesystem and what is best for them.  It is the opinion of many that making the starting offset 1mb as that is compatible with all storage vendors and allows for maximum portability should a migration be required from one vendor to another.  MS has elected to use the 1mb offset for Window 2k8 and Windows 7 and this is a move in the right direction.

Please have a look at Vaughn Stewarts blogs which he details alignement and provides links to others documentation.

http://blogs.netapp.com/virtualstorageguy/2009/06/io-efficiency-and-alignment-the-cloud-demands-standards.html

http://blogs.netapp.com/virtualstorageguy/2010/04/raising-awareness-around-the-misalignment-of-data.html

Thanks,

Chris Gebhardt

View solution in original post

5 REPLIES 5

daniel_kaiser
3,934 Views

i also found another link that talks about 64 alignments.

http://communities.vmware.com/thread/162137

daniel_kaiser
3,934 Views

did a little more digging around the net and found a post on OS disk alignment on Netapp here.  per some of the comments it appears that it's up to you if you wanted to use either 32 or 64 alignments.  If this is the case then what is mbralign configured to use when you run it against a vmdk file?

http://blog.scottlowe.org/2009/03/31/storage-alignment-document/

chrisgeb
3,935 Views

I would say that either would work just fine however lets consider the standardization of alignment for the cloud.  Some vendors recommend different sizes based on their own filesystem and what is best for them.  It is the opinion of many that making the starting offset 1mb as that is compatible with all storage vendors and allows for maximum portability should a migration be required from one vendor to another.  MS has elected to use the 1mb offset for Window 2k8 and Windows 7 and this is a move in the right direction.

Please have a look at Vaughn Stewarts blogs which he details alignement and provides links to others documentation.

http://blogs.netapp.com/virtualstorageguy/2009/06/io-efficiency-and-alignment-the-cloud-demands-standards.html

http://blogs.netapp.com/virtualstorageguy/2010/04/raising-awareness-around-the-misalignment-of-data.html

Thanks,

Chris Gebhardt

daniel_kaiser
3,934 Views

If i'm interpretting everything correctly, 64 should be used even though 32 or 64 would work.  Thanks.

3,934 Views

OK some background first.

NetApp: The logical block size of NetApp storage is: 4KB

EMC: Logical block size is 64KB

So.....In my experience,

  • Windows 2008:
    • You do not need to align the disk as windows will altomatically do this for you. By default, for any disk larger than 4gb in size the partition alignment is 1mb. This is same in Vista and windows 7 too I beleieve. As this is properly divisible by 4KB and 64KB and all of their (when I say all, I mean most of its practically used) permutations, we are all good and no manual alignments are necessary.
  • Windows 2003:
    • Since windows 2003 and most other old OS's start their first logical partition at sector (logical block) 63,you need to manually align the disks and the starting offset should be something appropriately divisible by 4KB in NetApps case (so both 32 and 64KB would do) and 64KB in EMC's case (so 64KB for EMC)

Refer to the below document for a good understanding.

http://media.netapp.com/documents/tr-3747.pdf

Public