<?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 Re: VMware Swap File Autogrow FlexVol volumes in VMware Solutions Discussions</title>
    <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/VMware-Swap-File-Autogrow-FlexVol-volumes/m-p/43281#M4221</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Vince and welcome to the Communities! &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.netapp.com/4.0.8/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Autogrowing volumes is a part of a bigger picture of space management, so this is not necessarily specific to vShpere, swap files, etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The short answer is: your mileage may vary, as everyone has their own likes / dislikes re space management.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Volume autosize was mainly introduced to address the dilemma re volumes with LUNs &amp;amp; snapshots, where originally the best practice asked people to halve their usable capacity (simply speaking) to guarantee that LUNs will not go offline due to a lack of space in the volume.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are different ways of achieving pretty much the same goal - e.g. my favourite of oversizing significantly all volumes, setting space guarantee to none (thin provisioning) &amp;amp; monitoring free space on the aggregate level only (not everyone likes this approach though).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Radek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 07 Dec 2010 10:32:01 GMT</pubDate>
    <dc:creator>radek_kubka</dc:creator>
    <dc:date>2010-12-07T10:32:01Z</dc:date>
    <item>
      <title>VMware Swap File Autogrow FlexVol volumes</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/VMware-Swap-File-Autogrow-FlexVol-volumes/m-p/43277#M4220</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Everybody,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a little question for you guys, how you configure the swap datastore for for your environment ?&lt;/P&gt;&lt;P&gt;I have 3 ESXi 4.1 Server with 48 Gb RAM per ESXi and I have configured the swap datastore with 150 Gb.&lt;/P&gt;&lt;P&gt;I have read in the Best Practice Netapp VMware that's we can configure a option "Autogrow FlexVol volumes"&lt;/P&gt;&lt;P&gt;do you use this option?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;Vince&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:03:51 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/VMware-Swap-File-Autogrow-FlexVol-volumes/m-p/43277#M4220</guid>
      <dc:creator>vincent_m</dc:creator>
      <dc:date>2025-06-05T07:03:51Z</dc:date>
    </item>
    <item>
      <title>Re: VMware Swap File Autogrow FlexVol volumes</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/VMware-Swap-File-Autogrow-FlexVol-volumes/m-p/43281#M4221</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Vince and welcome to the Communities! &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.netapp.com/4.0.8/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Autogrowing volumes is a part of a bigger picture of space management, so this is not necessarily specific to vShpere, swap files, etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The short answer is: your mileage may vary, as everyone has their own likes / dislikes re space management.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Volume autosize was mainly introduced to address the dilemma re volumes with LUNs &amp;amp; snapshots, where originally the best practice asked people to halve their usable capacity (simply speaking) to guarantee that LUNs will not go offline due to a lack of space in the volume.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are different ways of achieving pretty much the same goal - e.g. my favourite of oversizing significantly all volumes, setting space guarantee to none (thin provisioning) &amp;amp; monitoring free space on the aggregate level only (not everyone likes this approach though).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Radek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Dec 2010 10:32:01 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/VMware-Swap-File-Autogrow-FlexVol-volumes/m-p/43281#M4221</guid>
      <dc:creator>radek_kubka</dc:creator>
      <dc:date>2010-12-07T10:32:01Z</dc:date>
    </item>
    <item>
      <title>Re: VMware Swap File Autogrow FlexVol volumes</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/VMware-Swap-File-Autogrow-FlexVol-volumes/m-p/43285#M4222</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Okay !&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So it's for you the good option like I have configured my datastore ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Vince&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Dec 2010 13:13:44 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/VMware-Swap-File-Autogrow-FlexVol-volumes/m-p/43285#M4222</guid>
      <dc:creator>vincent_m</dc:creator>
      <dc:date>2010-12-07T13:13:44Z</dc:date>
    </item>
  </channel>
</rss>

