<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Performance: Thin Provisioning</title>
	<atom:link href="http://www.yellow-bricks.com/2009/11/15/performance-thin-provisioning/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.yellow-bricks.com/2009/11/15/performance-thin-provisioning/</link>
	<description>Building blocks for virtualization...</description>
	<lastBuildDate>Thu, 11 Mar 2010 09:21:29 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Carl L</title>
		<link>http://www.yellow-bricks.com/2009/11/15/performance-thin-provisioning/comment-page-1/#comment-5265</link>
		<dc:creator>Carl L</dc:creator>
		<pubDate>Mon, 23 Nov 2009 14:57:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=4539#comment-5265</guid>
		<description>On the NFS question: I suspect that if you do an eager thick disk that the NFS server will have to fully allocate the space since the VMKernel will write zero&#039;s to the entire disk.  Never tried it though.</description>
		<content:encoded><![CDATA[<p>On the NFS question: I suspect that if you do an eager thick disk that the NFS server will have to fully allocate the space since the VMKernel will write zero&#8217;s to the entire disk.  Never tried it though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dennis</title>
		<link>http://www.yellow-bricks.com/2009/11/15/performance-thin-provisioning/comment-page-1/#comment-5180</link>
		<dc:creator>Dennis</dc:creator>
		<pubDate>Wed, 18 Nov 2009 21:20:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=4539#comment-5180</guid>
		<description>any idea if there is a big difference between vmfs version 3.31 and 3.33? Most customers will not upgrade vmfs but use the ESX 3.5 vmfs version. Many documents show that some of the metadata layout changes regarding minimized SCSI reservations were on 3.33.</description>
		<content:encoded><![CDATA[<p>any idea if there is a big difference between vmfs version 3.31 and 3.33? Most customers will not upgrade vmfs but use the ESX 3.5 vmfs version. Many documents show that some of the metadata layout changes regarding minimized SCSI reservations were on 3.33.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Duncan Epping</title>
		<link>http://www.yellow-bricks.com/2009/11/15/performance-thin-provisioning/comment-page-1/#comment-5179</link>
		<dc:creator>Duncan Epping</dc:creator>
		<pubDate>Wed, 18 Nov 2009 19:34:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=4539#comment-5179</guid>
		<description>Fragmentation is not an issue as usually blocks (read/write) requests from the OS are smaller than the thin chunks.</description>
		<content:encoded><![CDATA[<p>Fragmentation is not an issue as usually blocks (read/write) requests from the OS are smaller than the thin chunks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dennis</title>
		<link>http://www.yellow-bricks.com/2009/11/15/performance-thin-provisioning/comment-page-1/#comment-5178</link>
		<dc:creator>Dennis</dc:creator>
		<pubDate>Wed, 18 Nov 2009 18:27:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=4539#comment-5178</guid>
		<description>What is about fragmentation when using Thin Provisioned disks? In my opinion there must be a fragmentation of VMFS after some time especially when overallocating.</description>
		<content:encoded><![CDATA[<p>What is about fragmentation when using Thin Provisioned disks? In my opinion there must be a fragmentation of VMFS after some time especially when overallocating.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daragh Naughton</title>
		<link>http://www.yellow-bricks.com/2009/11/15/performance-thin-provisioning/comment-page-1/#comment-5174</link>
		<dc:creator>Daragh Naughton</dc:creator>
		<pubDate>Wed, 18 Nov 2009 15:55:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=4539#comment-5174</guid>
		<description>A bit of digging revealed:

&quot;This behaviour of the VMware Infrastructure with a virtually provisioned NFS file system is a result of the NFS protocol, not of virtual provisioning. With NFS, storage for a Virtual Machine is not reserved in advance; it is reserved when data is actually written to the virtual machine. This is because the NFS protocol is thinly provisioned by default. Data blocks in the file system are allocated to the NFS client (ESX in this case) only when they are needed.&quot;

Source: &quot;Implementing Virtual Provisioning on EMC CLARiiON and Cellera with Virtual Infrastructure&quot;
http://www.emc.com/collateral/software/white-papers/h6131-implementing-vp-with-clariion-celerra-vmware-infrastructure-wp.pdf


So it is the NFS server that only allocates the blocks - it is absolutely nothing to do with the hypervisor. Interesting.</description>
		<content:encoded><![CDATA[<p>A bit of digging revealed:</p>
<p>&#8220;This behaviour of the VMware Infrastructure with a virtually provisioned NFS file system is a result of the NFS protocol, not of virtual provisioning. With NFS, storage for a Virtual Machine is not reserved in advance; it is reserved when data is actually written to the virtual machine. This is because the NFS protocol is thinly provisioned by default. Data blocks in the file system are allocated to the NFS client (ESX in this case) only when they are needed.&#8221;</p>
<p>Source: &#8220;Implementing Virtual Provisioning on EMC CLARiiON and Cellera with Virtual Infrastructure&#8221;<br />
<a href="http://www.emc.com/collateral/software/white-papers/h6131-implementing-vp-with-clariion-celerra-vmware-infrastructure-wp.pdf" rel="nofollow">http://www.emc.com/collateral/software/white-papers/h6131-implementing-vp-with-clariion-celerra-vmware-infrastructure-wp.pdf</a></p>
<p>So it is the NFS server that only allocates the blocks &#8211; it is absolutely nothing to do with the hypervisor. Interesting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Duncan</title>
		<link>http://www.yellow-bricks.com/2009/11/15/performance-thin-provisioning/comment-page-1/#comment-5156</link>
		<dc:creator>Duncan</dc:creator>
		<pubDate>Tue, 17 Nov 2009 14:10:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=4539#comment-5156</guid>
		<description>No clue, somehow we must be checking a setting which is passed on to the hypervisor. But this is what people have always told me. I actually never looked into it, took it for granted.</description>
		<content:encoded><![CDATA[<p>No clue, somehow we must be checking a setting which is passed on to the hypervisor. But this is what people have always told me. I actually never looked into it, took it for granted.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daragh Naughton</title>
		<link>http://www.yellow-bricks.com/2009/11/15/performance-thin-provisioning/comment-page-1/#comment-5155</link>
		<dc:creator>Daragh Naughton</dc:creator>
		<pubDate>Tue, 17 Nov 2009 13:19:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=4539#comment-5155</guid>
		<description>Hi Duncan,

Regarding NFS and VMDK provisioning, the ESX Config Guide on p.99 states (as you have quoted here):

&quot;The virtual disks that you create on NFS-based datastores use a disk format dictated by the NFS server&quot;

How can the NFS Server dictate this? Surely its the ESX Server&#039;s choice, based on the type of NFS etc?</description>
		<content:encoded><![CDATA[<p>Hi Duncan,</p>
<p>Regarding NFS and VMDK provisioning, the ESX Config Guide on p.99 states (as you have quoted here):</p>
<p>&#8220;The virtual disks that you create on NFS-based datastores use a disk format dictated by the NFS server&#8221;</p>
<p>How can the NFS Server dictate this? Surely its the ESX Server&#8217;s choice, based on the type of NFS etc?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Gray</title>
		<link>http://www.yellow-bricks.com/2009/11/15/performance-thin-provisioning/comment-page-1/#comment-5099</link>
		<dc:creator>Eric Gray</dc:creator>
		<pubDate>Sun, 15 Nov 2009 22:53:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=4539#comment-5099</guid>
		<description>The PDF will be listed on the VMware Technical Resource Center soon, it was just published Friday evening.  I know the writer and she tipped me off early... sometimes it pays to be a VCritical subscriber.  :-)

Eric</description>
		<content:encoded><![CDATA[<p>The PDF will be listed on the VMware Technical Resource Center soon, it was just published Friday evening.  I know the writer and she tipped me off early&#8230; sometimes it pays to be a VCritical subscriber.  <img src='http://www.yellow-bricks.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Eric</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Duncan</title>
		<link>http://www.yellow-bricks.com/2009/11/15/performance-thin-provisioning/comment-page-1/#comment-5098</link>
		<dc:creator>Duncan</dc:creator>
		<pubDate>Sun, 15 Nov 2009 22:42:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=4539#comment-5098</guid>
		<description>No clue, I noticed the link on another blog...</description>
		<content:encoded><![CDATA[<p>No clue, I noticed the link on another blog&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Smith</title>
		<link>http://www.yellow-bricks.com/2009/11/15/performance-thin-provisioning/comment-page-1/#comment-5092</link>
		<dc:creator>Jason Smith</dc:creator>
		<pubDate>Sun, 15 Nov 2009 15:58:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=4539#comment-5092</guid>
		<description>Selecting &quot;Support clustering features such as Fault Tolerance&quot; when creating a VMDK will provision it eager zeroed thick.</description>
		<content:encoded><![CDATA[<p>Selecting &#8220;Support clustering features such as Fault Tolerance&#8221; when creating a VMDK will provision it eager zeroed thick.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
