 




<?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: Vmware vmdk file converting problem</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/vmware-vmdk-file-converting-problem/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/vmware-vmdk-file-converting-problem/</link>
	<description></description>
	<lastBuildDate>Tue, 21 May 2013 23:11:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: radyair</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/vmware-vmdk-file-converting-problem/#comment-79362</link>
		<dc:creator>radyair</dc:creator>
		<pubDate>Mon, 19 Jul 2010 19:16:06 +0000</pubDate>
		<guid isPermaLink="false">#comment-79362</guid>
		<description><![CDATA[It is possible to use vmkfstools to convert vmdk&#039;s.

From your error message (Destination disk format: VMFS zeroedthick),
and this concise summary of vmkfstools:

&lt;a href=&quot;http://avarcher.net/esx3guide/VMKFSTOOLS.htm&quot;&gt;http://avarcher.net/esx3guide/VMKFSTOOLS.htm&lt;/a&gt;

I think you are trying to open a workstation image that is thin and convert into one that is thick. That is, the workstation allowed the vmdk to start small and grow to it&#039;s specified size, but the new file is being created at it&#039;s allocated size, all at once.

I would experiment with the FILE SYSTEM UPGRADE OPTIONS as follows:

VMFS-2 to VMFS-3 file system upgrade is a two step process. Before file system upgrade can begin the `vmfs2` and `vmfs3` drivers must be unloaded and the auxiliary file system driver, `fsaux`, should be loaded. The first step of upgrade uses the `-T` option. Once the first step completes, the auxiliary file system driver, `fsaux`, must be unloaded and the `vmfs2` and `vmfs3` drivers reloaded. The second step of file system upgrade makes use of the `-u` option.

-T , -tovmfs3

-x , -upgradetype [zeroedthick&#124;eagerzeroedthick&#124;thin] 

Also, note the requirement to load the fsaux driver before starting the upgrade.

Hope this helps]]></description>
		<content:encoded><![CDATA[<p>It is possible to use vmkfstools to convert vmdk&#8217;s.</p>
<p>From your error message (Destination disk format: VMFS zeroedthick),<br />
and this concise summary of vmkfstools:</p>
<p><a href="http://avarcher.net/esx3guide/VMKFSTOOLS.htm">http://avarcher.net/esx3guide/VMKFSTOOLS.htm</a></p>
<p>I think you are trying to open a workstation image that is thin and convert into one that is thick. That is, the workstation allowed the vmdk to start small and grow to it&#8217;s specified size, but the new file is being created at it&#8217;s allocated size, all at once.</p>
<p>I would experiment with the FILE SYSTEM UPGRADE OPTIONS as follows:</p>
<p>VMFS-2 to VMFS-3 file system upgrade is a two step process. Before file system upgrade can begin the `vmfs2` and `vmfs3` drivers must be unloaded and the auxiliary file system driver, `fsaux`, should be loaded. The first step of upgrade uses the `-T` option. Once the first step completes, the auxiliary file system driver, `fsaux`, must be unloaded and the `vmfs2` and `vmfs3` drivers reloaded. The second step of file system upgrade makes use of the `-u` option.</p>
<p>-T , -tovmfs3</p>
<p>-x , -upgradetype [zeroedthick|eagerzeroedthick|thin] </p>
<p>Also, note the requirement to load the fsaux driver before starting the upgrade.</p>
<p>Hope this helps</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: eliyevelxan</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/vmware-vmdk-file-converting-problem/#comment-79350</link>
		<dc:creator>eliyevelxan</dc:creator>
		<pubDate>Mon, 19 Jul 2010 08:18:21 +0000</pubDate>
		<guid isPermaLink="false">#comment-79350</guid>
		<description><![CDATA[Hi. I have test.vmdk workstation file. I wand convert for esxserver 4.0 . I tryed it by vmkfstools. i writed like that

vmkfstools -i test.vmdk edomain.vmdk

But i get the error  

[root@ESX Edomain]# vmkfstools -i test.vmdk edomain.vmdk Destination disk format: VMFS zeroedthick Failed to open &#039;test.vmdk&#039;: Broken pipe (2097161).

The directory is right

Then i tried to do this instruction

http://communities.vmware.com/thread/227143;jsessionid=2DA3CAB1E4F583CEC8887DDB6144C151?tstart=0

But the problem not resolved. The system cannot recognized the file after operation vmware-vdiskmanager. Please help]]></description>
		<content:encoded><![CDATA[<p>Hi. I have test.vmdk workstation file. I wand convert for esxserver 4.0 . I tryed it by vmkfstools. i writed like that</p>
<p>vmkfstools -i test.vmdk edomain.vmdk</p>
<p>But i get the error  </p>
<p>[root@ESX Edomain]# vmkfstools -i test.vmdk edomain.vmdk Destination disk format: VMFS zeroedthick Failed to open &#8216;test.vmdk&#8217;: Broken pipe (2097161).</p>
<p>The directory is right</p>
<p>Then i tried to do this instruction</p>
<p><a href="http://communities.vmware.com/thread/227143;jsessionid=2DA3CAB1E4F583CEC8887DDB6144C151?tstart=0" rel="nofollow">http://communities.vmware.com/thread/227143;jsessionid=2DA3CAB1E4F583CEC8887DDB6144C151?tstart=0</a></p>
<p>But the problem not resolved. The system cannot recognized the file after operation vmware-vdiskmanager. Please help</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 3/8 queries in 0.059 seconds using memcached
Object Caching 283/284 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-22 00:08:19 -->