<?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 Is ONTAP thin friendly ? in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Is-ONTAP-thin-friendly/m-p/165666#M37867</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;We have a few FAS8200s that are using HPE 3PAR for storage, by default the volumes on the 3PAR are thin provisioned to the FAS8200s.&lt;/P&gt;&lt;P&gt;Is ONTAP friendly towards thin volumes provisioned to it from 3rd party arrays ?&amp;nbsp; So if data is deleted on a filer volume will it perform the equivalent of an unmap command to let the array know that blocks can be reclaimed ?&lt;/P&gt;&lt;P&gt;Or is there a way to write zeros to the freespace on a volume/aggregate so that the storage array can claim back space and make the volume thinner ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2025 10:28:25 GMT</pubDate>
    <dc:creator>Markinnz</dc:creator>
    <dc:date>2025-06-04T10:28:25Z</dc:date>
    <item>
      <title>Is ONTAP thin friendly ?</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Is-ONTAP-thin-friendly/m-p/165666#M37867</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;We have a few FAS8200s that are using HPE 3PAR for storage, by default the volumes on the 3PAR are thin provisioned to the FAS8200s.&lt;/P&gt;&lt;P&gt;Is ONTAP friendly towards thin volumes provisioned to it from 3rd party arrays ?&amp;nbsp; So if data is deleted on a filer volume will it perform the equivalent of an unmap command to let the array know that blocks can be reclaimed ?&lt;/P&gt;&lt;P&gt;Or is there a way to write zeros to the freespace on a volume/aggregate so that the storage array can claim back space and make the volume thinner ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 10:28:25 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Is-ONTAP-thin-friendly/m-p/165666#M37867</guid>
      <dc:creator>Markinnz</dc:creator>
      <dc:date>2025-06-04T10:28:25Z</dc:date>
    </item>
    <item>
      <title>Re: Is ONTAP thin friendly ?</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Is-ONTAP-thin-friendly/m-p/165668#M37868</link>
      <description>&lt;P&gt;Hello Markinnz,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes, ONTAP does support thin provisioning on the backend and does perform SCSI unmap with supported 3rd party backend. Please verify the compatibility on&amp;nbsp;&lt;A href="https://mysupport.netapp.com/matrix/#welcome" target="_self"&gt;NetApp Interoperability Matrix&lt;/A&gt;.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Team NetApp&lt;/P&gt;</description>
      <pubDate>Tue, 06 Apr 2021 03:25:59 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Is-ONTAP-thin-friendly/m-p/165668#M37868</guid>
      <dc:creator>ttran</dc:creator>
      <dc:date>2021-04-06T03:25:59Z</dc:date>
    </item>
    <item>
      <title>Re: Is ONTAP thin friendly ?</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Is-ONTAP-thin-friendly/m-p/165669#M37869</link>
      <description>&lt;P&gt;Excellent!&lt;/P&gt;&lt;P&gt;Are there any commands that show what back end array capabilities are available to the FAS8200 ?&amp;nbsp; To see if the FAS knows it can use unmap and is using it ?&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 06 Apr 2021 04:05:51 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Is-ONTAP-thin-friendly/m-p/165669#M37869</guid>
      <dc:creator>Markinnz</dc:creator>
      <dc:date>2021-04-06T04:05:51Z</dc:date>
    </item>
  </channel>
</rss>

