<?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: Multiple VMFS volumes per LUN = Not a Good Idea</title>
	<atom:link href="http://www.punchingclouds.com/?feed=rss2&#038;p=1020" rel="self" type="application/rss+xml" />
	<link>http://www.punchingclouds.com/?p=1020</link>
	<description>Breakthroughs in the Field of Virtualization, Cloud Computing and other Cool Shit!</description>
	<lastBuildDate>Tue, 13 Jul 2010 07:23:49 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Bill Griffith</title>
		<link>http://www.punchingclouds.com/?p=1020&#038;cpage=1#comment-420</link>
		<dc:creator>Bill Griffith</dc:creator>
		<pubDate>Mon, 08 Mar 2010 17:31:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.punchingclouds.com/?p=1020#comment-420</guid>
		<description>Derek, why not just do a volume grow? Then you don&#039;t have to worry about metadata, locks, multiple luns etc...</description>
		<content:encoded><![CDATA[<p>Derek, why not just do a volume grow? Then you don&#8217;t have to worry about metadata, locks, multiple luns etc&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Griffith</title>
		<link>http://www.punchingclouds.com/?p=1020&#038;cpage=1#comment-419</link>
		<dc:creator>Bill Griffith</dc:creator>
		<pubDate>Mon, 08 Mar 2010 17:05:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.punchingclouds.com/?p=1020#comment-419</guid>
		<description>This doc doesn&#039;t explicitly talk about the locking mechanism (where is that doc???) it does talk about performance of thin vs thick provisioned disks.

www.vmware.com/pdf/vsp_4_thinprov_perf.pdf</description>
		<content:encoded><![CDATA[<p>This doc doesn&#8217;t explicitly talk about the locking mechanism (where is that doc???) it does talk about performance of thin vs thick provisioned disks.</p>
<p><a href="http://www.vmware.com/pdf/vsp_4_thinprov_perf.pdf" rel="nofollow">http://www.vmware.com/pdf/vsp_4_thinprov_perf.pdf</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Coral Balla</title>
		<link>http://www.punchingclouds.com/?p=1020&#038;cpage=1#comment-405</link>
		<dc:creator>Coral Balla</dc:creator>
		<pubDate>Fri, 05 Mar 2010 09:41:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.punchingclouds.com/?p=1020#comment-405</guid>
		<description>I like the layout of your blog and I&#039;m going to do the same thing for mine.  Do you have any tips? Please PM ME on yahoo @ AmandaLovesYou702</description>
		<content:encoded><![CDATA[<p>I like the layout of your blog and I&#8217;m going to do the same thing for mine.  Do you have any tips? Please PM ME on yahoo @ AmandaLovesYou702</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Derek</title>
		<link>http://www.punchingclouds.com/?p=1020&#038;cpage=1#comment-390</link>
		<dc:creator>Derek</dc:creator>
		<pubDate>Mon, 01 Mar 2010 18:36:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.punchingclouds.com/?p=1020#comment-390</guid>
		<description>That makes sense as it relates to multiple datastores, but is this really relevant if the multiple VMFS partitions are different extents of the same VMFS datastore?

An example I have had is a LUN on an iSCSI enclosure is created, a VMFS file system and partition on the LUN. Later we needed more space so we extended the LUN, then added a VMFS extent to the LUN. I could have added another LUN with the free space and then added an extent there, but I have had issues on occasion with other storage admins deleting LUN&#039;s they think are not in used, leaving me with a damaged VMFS file system. That is another story. In any case, is there any issue you could think of with 2 extents of the same VMFS on one extended LUN? The fact that both Extents locked at the same time shouldn&#039;t be any more issue than if it was one extent. Either way all the space would be locked.

Just curious to your opinion.</description>
		<content:encoded><![CDATA[<p>That makes sense as it relates to multiple datastores, but is this really relevant if the multiple VMFS partitions are different extents of the same VMFS datastore?</p>
<p>An example I have had is a LUN on an iSCSI enclosure is created, a VMFS file system and partition on the LUN. Later we needed more space so we extended the LUN, then added a VMFS extent to the LUN. I could have added another LUN with the free space and then added an extent there, but I have had issues on occasion with other storage admins deleting LUN&#8217;s they think are not in used, leaving me with a damaged VMFS file system. That is another story. In any case, is there any issue you could think of with 2 extents of the same VMFS on one extended LUN? The fact that both Extents locked at the same time shouldn&#8217;t be any more issue than if it was one extent. Either way all the space would be locked.</p>
<p>Just curious to your opinion.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
