<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic VMware + Dedup question in VMware Solutions Discussions</title>
    <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/VMware-Dedup-question/m-p/61028#M5764</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have a FAS3140 with a 3 TB volume with 3 1TB LUN's in the volume. The LUN and volume are thin provisioned with space savings being pushed back into the aggr. I sent my ESX admin a DF on his volume because he said he is running low on space. Why is ESX reporting that he only has a 200 GB in the datastore to create additional VMDK but the array is reporting 1831 GB? ESX server is 4.0 and they use thick VMDKs?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline; font-family: Calibri; "&gt;Filesystem&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; total&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; used&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; avail&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; capacity&amp;nbsp; Mounted on&lt;/SPAN&gt; &lt;BR /&gt;&lt;SPAN style="font-family: Calibri;"&gt;/vol/esxvol1/&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 3072GB&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1240GB&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1831GB&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 40%&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /vol/esxvol1/&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2025 07:11:13 GMT</pubDate>
    <dc:creator>mjgalloway</dc:creator>
    <dc:date>2025-06-05T07:11:13Z</dc:date>
    <item>
      <title>VMware + Dedup question</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/VMware-Dedup-question/m-p/61028#M5764</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have a FAS3140 with a 3 TB volume with 3 1TB LUN's in the volume. The LUN and volume are thin provisioned with space savings being pushed back into the aggr. I sent my ESX admin a DF on his volume because he said he is running low on space. Why is ESX reporting that he only has a 200 GB in the datastore to create additional VMDK but the array is reporting 1831 GB? ESX server is 4.0 and they use thick VMDKs?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline; font-family: Calibri; "&gt;Filesystem&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; total&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; used&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; avail&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; capacity&amp;nbsp; Mounted on&lt;/SPAN&gt; &lt;BR /&gt;&lt;SPAN style="font-family: Calibri;"&gt;/vol/esxvol1/&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 3072GB&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1240GB&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1831GB&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 40%&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /vol/esxvol1/&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:11:13 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/VMware-Dedup-question/m-p/61028#M5764</guid>
      <dc:creator>mjgalloway</dc:creator>
      <dc:date>2025-06-05T07:11:13Z</dc:date>
    </item>
    <item>
      <title>Re: VMware + Dedup question</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/VMware-Dedup-question/m-p/61033#M5765</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;LUNs that are deduplicated cannot realize the space savings gained by deduplication.&amp;nbsp; LUNs are a logical presentation of a SCSI disk drive, which have no correlation between the LUN's formatted filesystem and WAFL.&amp;nbsp; If you want your ESX admin to see the deduplicated space, migrate your VMDKs to NFS if possible.&amp;nbsp; NFS datastores are WAFL so the space savings from deduplication can be realized by ESX.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mitchell&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Aug 2010 03:34:51 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/VMware-Dedup-question/m-p/61033#M5765</guid>
      <dc:creator>mitchells</dc:creator>
      <dc:date>2010-08-03T03:34:51Z</dc:date>
    </item>
  </channel>
</rss>

