Storage Basics – Part VII: Storage Alignment

StorageBasics7At the risk of beating a dead horse, it’s time to resurrect my Storage Basics series.  I’ve recently had some great feedback on the series and figured I should round out a few of the concepts before I wrap it up.  I want to cover a topic often discussed amongst virtualization professionals, but one I often find general practitioners and server admins not understanding: storage alignment.  Storage alignment, or the lack of alignment, is not a new issue and is not unique to VMware or virtualization in general.  However, the effects of misaligned storage can be more greatly felt in terms of reduced performance and strain on a storage system in shared, oversubscribed or high I/O environments.  Many others in the virtualization and storage communities have already covered partition alignment (see Duncan Epping, Vaughn Stewart, and most recently Chad Sakac), but I feel it is an important enough topic for me to re-hash as part of this series.

What is Storage Alignment?

Let’s start with a quick overview of what storage alignment means.  Quite simply, storage alignment refers to the positioning (starting offset) of the various pieces of a systems storage components – the physical disk sectors or array’s chunks, the VMware File System (VMFS) in a VMware environment, and the guest file system’s clusters within a partition – in relation to the layer directly under the element in question.  A quick graphic often makes quick work of explaining this (I often whiteboard this concept for colleagues and clients):

partition alignment conceptual diagram

As you can see, the starting offset of the VMFS partition does not correspond to the physical segmentation of the underlying disks (in this case, the chunks on a SAN – but could be conceptually replaced with the sectors of a single disk).  Furthermore, the clusters (or blocks) of the guest VM are not aligned to the VMFS partition nor to the underlying storage.  For traditional (physical) systems or VMware RDM’s, the VMFS layer could be abstracted, but the result would be the same – the clusters of a partition would be misaligned to the underlying disk.

What Does it Mean?

Quite simply, misaligned storage (both VMFS partitions and Guest File Systems) can lead to poor performance under certain conditions.  How badly performance is impacted depends on the degree of I/O strain your server and storage are under, the caching mechanisms in your environment, and the architecture of your SAN.  Again, a visual can help explain how misaligned storage can hurt you. For simplicity let’s leave out the VMFS layer as we consider the following diagram (pardon my hasty Visio visualization):

What we see is that the target data in a tiny 16kb read request spans two 64kb chunks on our storage array.  Any reads of that piece of data will result in twice the amount of data as would be minimally necessary being transferred to the host’s storage stack.  The net effect is an increase in the work the storage array must do – gobbling up IOPS that would otherwise be available for the real work of reading data, reducing throughput on the interface, and messing with cache algorithms and dedupe mechanisms on some arrays.  In short, misaligned storage is an efficiency killer.  Now add in the VMFS layer back in and you’ll see how things get complicated.

If (and we’re talking a big IF here) every bit of data you wanted to read spanned a chunk or sector boundary, you could experience half the expected performance due to misalignment.  In reality, depending on your workload and storage technology your performance increase from properly aligning your storage will probably be somewhere between 10-30%.

Want to dig deeper?

There have been some great resources published on this issue over the past few years on storage alignment.  Major vendors have all begun pushing information on the problem – here are some of the best that I have found:

Microsoft has a Knowledge Base article ( that describes the problem and symptoms of misaligned partitions, how to determine if your partition is aligned, and the use of diskpart to create aligned partitions.

Microsoft also has an in-depth article on MSDN, including some performance numbers at  Also check out Jimmy May’s series Partition (Sector) alignment for SQL Server here:  One of the best descriptions of the complexities of the problem can be found in Jimmy’s blog series.  Microsoft has a KB article that describes performance problems when disk partitions are misaligned here:, including the formulas to calculate if your existing partitions are correctly aligned.

VMware has an article here:  Be aware that this article is for Virtual Infrastructure 3, not vSphere 4.0.  Some of the information is now a bit dated.

Netapp has a few documents to check out: (VI3), and (vSphere)

EMC covers alignment in their TechBooks for Clariion, Celerra, and Symmetrix.

Tools to Align Partitions:

Ok – so you’ve bought into this whole partition alignment thing as being a real issue.  How to you fix it?  Here are some tools:

  1. MSInfo32.exe, wmic, and dmdiag will show you misaligned partitions on Windows machines (check the Microsoft links above for usage info).
  2. Diskpart.exe (or diskpar.exe on versions of Windows previous to 2003) creates aligned partitions on Windows systems.  Diskpart cannot be used to realign a previously created partition, only to create new correctly aligned partitions.
  3. MBRScan/MBRAlign from NetApp can report on and realign existing virtual disks on a VMware ESX server.  Also a nifty PowerShell script from NetApp to find if your partitions are aligned:
  4. vOptimizer from Vizioncore can report on and realign existing virtual disks.
  5. GParted can be used to create aligned partitions on both Windows and Linux machines, and to realign some existing partitions.
  6. VMware vCenter – VMFS datastores created using vCenter are aligned automatically. Note – Guest VMDK’s are not aligned automatically by vCenter – you must manually create aligned partitions on your VMDK’s or use a Guest OS that creates properly aligned partitions (Windows 2008 and later).

Best Practices:

Before I wrap this installment up, here are some best practices for storage alignment in your environment:

  • Create aligned partitions in your VMware templates. Do it once, do it right – every machine you deploy from the template will be aligned.
  • Use caution with tools like Symantec Ghost.  Ghost can take images of aligned partitions and misalign them when laying down on a new system.
  • Use caution when performing P2V’s using VMware vCenter Converter – it does not align guest disks on import.  You might consider using Converter to perform a P2V of the system disk only, then create new VMDK’s on the converted guest.  Use Diskpart, gparted, or another tool to create aligned partitions on the new VMDK’s and finally copy the data over to the newly virtualized server using a tool like Robocopy, RichCopy, or rsync.
  • SSD’s are particularly sensitive to misalignment, leading to poor performance and excessive wear.
  • Local VMFS volumes created by the ESX installer are not aligned.  If you are using an installer-created local VMFS for anything where performance matters, you might consider re-creating it through vCenter.
  • Watch out when attaching a data disk from an older VM to a new VM.  For example, you are upgrading your SQL servers to Windows 2008 R2 from 2003.  You decide to do a side-by-side upgrade, using the detach/attach method.  You install (or better yet, deploy from template) a new Windows 2008 R2 VM, detach your databases from the old server, move your SQL data and log virtual disks from your 2003 VM to the new VM and attach the SQL DB’s on the new server.  Those old VMDK’s may be misaligned!  Consider using Robocopy, RichCopy or rsync to ensure an aligned disk.
  • Check your storage vendors best practices for your particular environment (OS, workload, SAN, etc.).
  • There is some debate on whether or not it is advised to align your OS partitions.  There is no clear-cut answer on this as it depends so much on your environment and particular needs.  For help in deciding if you should align your Guest OS drives, see the comments in the blogs by Duncan Epping, Vaughn Stewart, and Chad Sakac.
  • While working the VMware User Group booth at the Washington, DC Virtualization Forum 2010 I had a user ask me if rules and procedures for alignment on 4k sector disks are different. I forgot to research it until just now, so I honestly don’t know (please comment if you do know!).  Check with your storage vendor if this is an issue for you.
  • Finally, you can’t realign partitions using tools like mbralign or vOptimizer in ESXi -Aaaron Delp explains the problem here:

I hope this is helpful for you in understanding the problem of storage alignment and how it can impact your environment.  Comments or questions are welcomed!

Keep Reading:


  1. From the esx3_partition_alignment pdf on page 3:

    “Note: Aligning the boot disk in the virtual machine is neither recommended nor required.
    Align only the data disks in the virtual machine.”

    If they go through the trouble of stating it in the document, it should probably not be done for the OS drives.

    • Harley – I agree for most use cases. The general consensus seems to be that it is not worth the time and effort to correct existing VM boot disks, but any new VM’s should be properly aligned.
      I would recommend aligning Windows XP VMware View VM’s boot disks (done automatically if using Vista or Windows 7), and any server VM’s boot disk if (for whatever reason) the boot disk is used for heavy I/O.
      Thanks for the comment!

  2. I recommend the fast and easy supergrubdisk be put under ‘tools’ – the easiest way to fix linux grub after using mbralign. Won’t fix if you have LVM, remove LVM first via a V2V conversion or dd.

  3. Excellent white paper on Paragon Software’s alignment tool here:

  4. Thank you for this article, and the references it contains. It’s useful.

    It seems that the root cause of misalignement is a forgotten myth. I can’t find any references about it. Plenty of poeple are explaining why we have to align, but nobody talks about why the hell it works that way.

    If I undertsand the story correctly, disk manufacturers reserve sector 0 to 63, and file system editors reserve sectors 1 to 64, generating the misalignement issue.

    Also, I cannot find information about using extended partition. I was told a long time ago that if you make a single extended partition on a drive containing logical drives, you may not need to align. But I can’t get why as the MBR is present anyway.


  1. […] This post was mentioned on Twitter by Todd Scalzott, Josh Townsend. Josh Townsend said: New post: Storage Basics – Part VII: Storage Alignment #vmware […]

  2. […] machine demand a lot of disk resources. For more information on the importance of alignment VMware Converter will not align your virtual disk files. PlateSpin Migrate will align the virtual […]

  3. […] widely discussed by both vendors (VMware, EMC, NetApp, Microsoft) and bloggers like Duncan Epping, Josh Townsend and Chad Sakac. The depth of the discussion makes it clear there’s a very real and difficult […]

  4. […] and Coalescing (VM Today) Storage Basics – Part VI: Storage Workload Characterization (VM Today) Storage Basics – Part VII: Storage Alignment (VM Today) vSphere and 2TB LUNs – changes from VI3.x (Virtual Geek) A look at the ESX I/O stack […]

  5. […] about Storage Alignment – how does a misaligned partition cause this math to get funky?  Hint: 2 blocks being […]

  6. […] Storage Basics – Part VII: Storage Alignment […]

  7. […] Storage Basics – Part VII: Storage Alignment […]

  8. […] Storage Basics – Part VII: Storage Alignment […]

  9. […] Storage Basics – Part VII: Storage Alignment […]

  10. […] Storage Basics – Part VII: Storage Alignment […]

Drop a comment below: