<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Scsi on Evan Hoffman</title><link>https://evan.wtf/tags/scsi/</link><description>Recent content in Scsi on Evan Hoffman</description><generator>Hugo</generator><language>en-US</language><copyright>Evan Hoffman</copyright><lastBuildDate>Mon, 24 Oct 2011 15:20:51 +0000</lastBuildDate><atom:link href="https://evan.wtf/tags/scsi/index.xml" rel="self" type="application/rss+xml"/><item><title>Rescan SATA bus (aka hot-adding a SATA disk on a Linux guest in VMware without rebooting)</title><link>https://evan.wtf/2011/10/24/rescan-sata-bus-aka-hot-adding-a-sata-disk-on-a-linux-guest-in-vmware-without-rebooting/</link><pubDate>Mon, 24 Oct 2011 15:20:51 +0000</pubDate><guid>https://evan.wtf/2011/10/24/rescan-sata-bus-aka-hot-adding-a-sata-disk-on-a-linux-guest-in-vmware-without-rebooting/</guid><description>&lt;p&gt;Linux supports hot-adding disks but whenever I add a new vdisk in VMware the new disk doesn&amp;rsquo;t show up unless I reboot, which defeats the purpose of hot-add. This command forces a rescan of the bus:&lt;/p&gt;&#10;&lt;pre tabindex="0"&gt;&lt;code&gt;echo &amp;#34;- - -&amp;#34; &amp;gt; /sys/class/scsi_host/host0/scan&#10;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;dmesg shows the new disk has been found:&lt;/p&gt;&#10;&lt;pre tabindex="0"&gt;&lt;code&gt;Vendor: VMware Model: Virtual disk Rev: 1.0 &#10; Type: Direct-Access ANSI SCSI revision: 02&#10; target0:0:2: Beginning Domain Validation&#10; target0:0:2: Domain Validation skipping write tests&#10; target0:0:2: Ending Domain Validation&#10; target0:0:2: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 127)&#10;SCSI device sdd: 1048576000 512-byte hdwr sectors (536871 MB)&#10;sdd: Write Protect is off&#10;sdd: Mode Sense: 03 00 00 00&#10;sdd: cache data unavailable&#10;sdd: assuming drive cache: write through&#10;SCSI device sdd: 1048576000 512-byte hdwr sectors (536871 MB)&#10;sdd: Write Protect is off&#10;sdd: Mode Sense: 03 00 00 00&#10;sdd: cache data unavailable&#10;sdd: assuming drive cache: write through&#10; sdd: unknown partition table&#10;sd 0:0:2:0: Attached scsi disk sdd&#10;sd 0:0:2:0: Attached scsi generic sg3 type 0&#10;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Now, why there&amp;rsquo;s no &amp;ldquo;rescan_sata&amp;rdquo; command is something I can&amp;rsquo;t fathom, but that&amp;rsquo;s Linux for you.&lt;/p&gt;</description></item><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>