<?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 Decreasing LUN containg VMFS datastore.. in VMware Solutions Discussions</title>
    <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Decreasing-LUN-containg-VMFS-datastore/m-p/67384#M6426</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Did you resize the Datastore in VMware also?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If yes:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In my opinion the only thing you can do is:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create a new 1.86TB lun and move all the VM's to the new LUN.&lt;/P&gt;&lt;P&gt;Finally remove the&amp;nbsp; 2.1TB lun.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you didn't resize / extend the datastore you can shrink the lun as long as the last datastore block is not changed &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 05 Aug 2011 09:32:35 GMT</pubDate>
    <dc:creator>jjbitservices</dc:creator>
    <dc:date>2011-08-05T09:32:35Z</dc:date>
    <item>
      <title>Decreasing LUN containg VMFS datastore..</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Decreasing-LUN-containg-VMFS-datastore/m-p/67379#M6425</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I ran into a serious problem today. One of our VMWare datastores ran out of disk space so I resized the Volume, then the LUN. I didn't pay attention to the maximum size Limit of 2TB for a VMFS datastore and received an error like:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Call "HostDatastoreSystem.QueryAvailableDisksForVmfs" for object "datastoreSystem-43668" on vCenter Server "" failed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;First I didn't even realize that this is related to the limitation of the datastore. And I started googling for the error and found nothing. What a suprise.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I resized the 1.86 TB LUN to 2.1 TB. All VM's are still running fine but now I wonder if I can decrease the size of the lun to 1.86TB without loosing or damaging the VMFS datastore?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Oliver&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:48:46 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/Decreasing-LUN-containg-VMFS-datastore/m-p/67379#M6425</guid>
      <dc:creator>oweinmann</dc:creator>
      <dc:date>2025-06-05T06:48:46Z</dc:date>
    </item>
    <item>
      <title>Decreasing LUN containg VMFS datastore..</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Decreasing-LUN-containg-VMFS-datastore/m-p/67384#M6426</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Did you resize the Datastore in VMware also?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If yes:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In my opinion the only thing you can do is:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create a new 1.86TB lun and move all the VM's to the new LUN.&lt;/P&gt;&lt;P&gt;Finally remove the&amp;nbsp; 2.1TB lun.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you didn't resize / extend the datastore you can shrink the lun as long as the last datastore block is not changed &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Aug 2011 09:32:35 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/Decreasing-LUN-containg-VMFS-datastore/m-p/67384#M6426</guid>
      <dc:creator>jjbitservices</dc:creator>
      <dc:date>2011-08-05T09:32:35Z</dc:date>
    </item>
    <item>
      <title>Decreasing LUN containg VMFS datastore..</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Decreasing-LUN-containg-VMFS-datastore/m-p/67389#M6427</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; If the VM's are important, then I think you should create a new 1.9 TB LUN, copy all the data and use this rather than taking the risk. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Once this is done you can try resizing the 2.1 TB lun &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.netapp.com/4.5.5/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Aug 2011 09:53:47 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/Decreasing-LUN-containg-VMFS-datastore/m-p/67389#M6427</guid>
      <dc:creator>arunchak</dc:creator>
      <dc:date>2011-08-05T09:53:47Z</dc:date>
    </item>
    <item>
      <title>Decreasing LUN containg VMFS datastore..</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Decreasing-LUN-containg-VMFS-datastore/m-p/67394#M6428</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi I didn't increase the vmfs datastore as I was not able to do that. So shrinking the lun should not harm the datastore?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Aug 2011 12:19:44 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/Decreasing-LUN-containg-VMFS-datastore/m-p/67394#M6428</guid>
      <dc:creator>oweinmann</dc:creator>
      <dc:date>2011-08-05T12:19:44Z</dc:date>
    </item>
    <item>
      <title>Decreasing LUN containg VMFS datastore..</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Decreasing-LUN-containg-VMFS-datastore/m-p/67399#M6429</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; What was the end result for you oweinmann?&amp;nbsp; I'm having the same issue as you had.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Oct 2011 13:17:54 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/Decreasing-LUN-containg-VMFS-datastore/m-p/67399#M6429</guid>
      <dc:creator>MENCHEGO1</dc:creator>
      <dc:date>2011-10-21T13:17:54Z</dc:date>
    </item>
    <item>
      <title>Decreasing LUN containg VMFS datastore..</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Decreasing-LUN-containg-VMFS-datastore/m-p/67403#M6430</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I agree with those that suggest a new LUN. If you shrink a lun you may not necessarily decrease its size by removing free blocks. You dont know where in the lun the free space is, so shrinking it to a smaller size may create more problems than it solves. I have had this same problem a few times and I always took the most cautious path by creating a new volume/lun and emptying the contents of the old before removing it entirely.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Nov 2011 19:23:10 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/Decreasing-LUN-containg-VMFS-datastore/m-p/67403#M6430</guid>
      <dc:creator>macmillangm</dc:creator>
      <dc:date>2011-11-02T19:23:10Z</dc:date>
    </item>
  </channel>
</rss>

