<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>2tb on Evan Hoffman</title><link>https://evan.wtf/tags/2tb/</link><description>Recent content in 2tb on Evan Hoffman</description><generator>Hugo</generator><language>en-US</language><copyright>Evan Hoffman</copyright><lastBuildDate>Fri, 24 Sep 2010 16:00:15 +0000</lastBuildDate><atom:link href="https://evan.wtf/tags/2tb/index.xml" rel="self" type="application/rss+xml"/><item><title>The VMware datastore LUN 2TB (well, 1.99999 TB) size limit</title><link>https://evan.wtf/2010/09/24/the-vmware-datastore-lun-2tb-well-1-99999-tb-size-limit/</link><pubDate>Fri, 24 Sep 2010 16:00:15 +0000</pubDate><guid>https://evan.wtf/2010/09/24/the-vmware-datastore-lun-2tb-well-1-99999-tb-size-limit/</guid><description>&lt;p&gt;I started migrating our physical machines to VMs using VMware a few years ago and the first problem I ran into is still the most annoying one: the size limit for LUNs is, &lt;a href="http://kb.vmware.com/kb/3371739"&gt;per VMware&amp;rsquo;s docs&lt;/a&gt;, (2TB - 512B). That&amp;rsquo;s 512 bytes shy of 2TB, so basically 1.99999 TB, or 2047.999 GB. So when I create a new LUN for a datastore in the SAN the max size is 2047 GB. Now, as the VMware KB article states, &lt;strong&gt;this is a limitation of SCSI, not VMware per se&lt;/strong&gt;, but that doesn&amp;rsquo;t make it any less annoying. When I first setup ESX, I created a 5 TB LUN for the datastore. It showed up in vCenter as 1 TB. After some Googling I learned of the 2 TB limit &amp;ndash; the usable space is basically usable space = (size of lun) % 2TB, where % is &lt;a href="http://en.wikipedia.org/wiki/Modulo_operation"&gt;the modulo operator&lt;/a&gt; &amp;ndash; and found something suggesting using extents to expand the datastore across luns. I did that, but I later learned that there seems to be a consensus that extents should be avoided.&lt;/p&gt;</description></item></channel></rss>