<?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 NetApp AFF A400 - NVMe Namespace, Volume Size and Overprovisioning (Ontap 9.13.1P1) in AFF</title>
    <link>https://community.netapp.com/t5/AFF/NetApp-AFF-A400-NVMe-Namespace-Volume-Size-and-Overprovisioning-Ontap-9-13-1P1/m-p/449668#M1230</link>
    <description>&lt;P&gt;Dear Community,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a question today regarding NVMe namespace and volume capacity in cooperation with VMware - NVMe oF FC 32 GBit/s. Version Ontap 9.13.1P1.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Our NetApp has Storage Efficency and compression active. Accordingly, the actually used storage of the volume is always much less than the NVMe namespace physically provides. However, since VMware only sees the storage that is made available via namespace using VMFS 6 and NVMe namespaces, we never have the opportunity to fully utilize the volume.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;What is best practice here to make this possible? Should the NVMe namespace simply be enlarged?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Example:&lt;/P&gt;&lt;P&gt;Volume - 5.2 TB, used storage 1.2TB&lt;BR /&gt;Namespace - 5 TB, used memory 4.8TB&lt;/P&gt;&lt;P&gt;Enlarge only namespace to 8 TB?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope you can help me. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2025 09:43:04 GMT</pubDate>
    <dc:creator>DirkE</dc:creator>
    <dc:date>2025-06-04T09:43:04Z</dc:date>
    <item>
      <title>NetApp AFF A400 - NVMe Namespace, Volume Size and Overprovisioning (Ontap 9.13.1P1)</title>
      <link>https://community.netapp.com/t5/AFF/NetApp-AFF-A400-NVMe-Namespace-Volume-Size-and-Overprovisioning-Ontap-9-13-1P1/m-p/449668#M1230</link>
      <description>&lt;P&gt;Dear Community,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a question today regarding NVMe namespace and volume capacity in cooperation with VMware - NVMe oF FC 32 GBit/s. Version Ontap 9.13.1P1.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Our NetApp has Storage Efficency and compression active. Accordingly, the actually used storage of the volume is always much less than the NVMe namespace physically provides. However, since VMware only sees the storage that is made available via namespace using VMFS 6 and NVMe namespaces, we never have the opportunity to fully utilize the volume.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;What is best practice here to make this possible? Should the NVMe namespace simply be enlarged?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Example:&lt;/P&gt;&lt;P&gt;Volume - 5.2 TB, used storage 1.2TB&lt;BR /&gt;Namespace - 5 TB, used memory 4.8TB&lt;/P&gt;&lt;P&gt;Enlarge only namespace to 8 TB?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope you can help me. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 09:43:04 GMT</pubDate>
      <guid>https://community.netapp.com/t5/AFF/NetApp-AFF-A400-NVMe-Namespace-Volume-Size-and-Overprovisioning-Ontap-9-13-1P1/m-p/449668#M1230</guid>
      <dc:creator>DirkE</dc:creator>
      <dc:date>2025-06-04T09:43:04Z</dc:date>
    </item>
  </channel>
</rss>

