<?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 Volume and Lun size in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Volume-and-Lun-size/m-p/69914#M16302</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The Block Access Management Guide for iSCSI and FC (bsag.pdf in the ONTAP documentation) gives a clearer answer... that if you don't have snapshots then the lun can be the size of the volume.&amp;nbsp; I tend to be more conservative but without snaps it states it is ok.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://now.netapp.com/NOW/knowledge/docs/ontap/rel801/html/ontap/bsag/GUID-35B62404-7D9B-4163-B43E-A5CDD9DDB399.html" target="_blank"&gt;http://now.netapp.com/NOW/knowledge/docs/ontap/rel801/html/ontap/bsag/GUID-35B62404-7D9B-4163-B43E-A5CDD9DDB399.html&lt;/A&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; If you are not using Snapshot copies, the size of your volume depends on the size of the LUNs...&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; The FlexVol volume should be at least as large as the size of the data to be contained by the volume.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P class="stepxmplabel"&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Example&lt;/STRONG&gt;&lt;/P&gt;&lt;P class="stepxmp"&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; If you need a traditional volume to contain two 200-GB LUNs, you should create the volume with enough disks to provide at least 400 GB of storage capacity.&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 30 Oct 2011 15:56:22 GMT</pubDate>
    <dc:creator>scottgelb</dc:creator>
    <dc:date>2011-10-30T15:56:22Z</dc:date>
    <item>
      <title>Volume and Lun size</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Volume-and-Lun-size/m-p/69904#M16300</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Everbody,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am been skeptical about the relationship between defining volume and LUN size for a quiet long time.&lt;/P&gt;&lt;P&gt;In our concern, we always used to create a volume 1 % higher than the LUN size.What was the use to create a volume in a such a way?&lt;/P&gt;&lt;P&gt;If in case we created a volume and Lun with same size whether it would create any problem? Please clarify.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Saran&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:42:20 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Volume-and-Lun-size/m-p/69904#M16300</guid>
      <dc:creator>saranraj456</dc:creator>
      <dc:date>2025-06-05T06:42:20Z</dc:date>
    </item>
    <item>
      <title>Volume and Lun size</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Volume-and-Lun-size/m-p/69909#M16301</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is some metadata so we like to keep at least 5-10% free in any container... so a volume 5-10% less than the volume size than the lun and at least 5-10% aggregate free space.. not always possible but good to have some wiggle room...leaves 10-20% free when keeping the aggr and volume with 5-10% each.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 29 Oct 2011 16:05:08 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Volume-and-Lun-size/m-p/69909#M16301</guid>
      <dc:creator>scottgelb</dc:creator>
      <dc:date>2011-10-29T16:05:08Z</dc:date>
    </item>
    <item>
      <title>Volume and Lun size</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Volume-and-Lun-size/m-p/69914#M16302</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The Block Access Management Guide for iSCSI and FC (bsag.pdf in the ONTAP documentation) gives a clearer answer... that if you don't have snapshots then the lun can be the size of the volume.&amp;nbsp; I tend to be more conservative but without snaps it states it is ok.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://now.netapp.com/NOW/knowledge/docs/ontap/rel801/html/ontap/bsag/GUID-35B62404-7D9B-4163-B43E-A5CDD9DDB399.html" target="_blank"&gt;http://now.netapp.com/NOW/knowledge/docs/ontap/rel801/html/ontap/bsag/GUID-35B62404-7D9B-4163-B43E-A5CDD9DDB399.html&lt;/A&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; If you are not using Snapshot copies, the size of your volume depends on the size of the LUNs...&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; The FlexVol volume should be at least as large as the size of the data to be contained by the volume.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P class="stepxmplabel"&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Example&lt;/STRONG&gt;&lt;/P&gt;&lt;P class="stepxmp"&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; If you need a traditional volume to contain two 200-GB LUNs, you should create the volume with enough disks to provide at least 400 GB of storage capacity.&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 30 Oct 2011 15:56:22 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Volume-and-Lun-size/m-p/69914#M16302</guid>
      <dc:creator>scottgelb</dc:creator>
      <dc:date>2011-10-30T15:56:22Z</dc:date>
    </item>
  </channel>
</rss>

