<?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: Query Not Zeroed disks in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Query-Not-Zeroed-disks/m-p/144835#M32139</link>
    <description>&lt;P&gt;I guess that, when you destroy an aggregate, the data that is still there is not really erased but made unavailable for access.&amp;nbsp;&amp;nbsp;When you really want that the disks do not contain any data when the storage is end of use, you have to sanitize disks....&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Spare disks can be added to an aggregate, can be used for creating a new one.... But in all cases the disks must contain only zeros. Adding zeros does not affect parity calculation. So that way we can hot-add disks,that's why zeroing is needed.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 22 Nov 2018 16:53:25 GMT</pubDate>
    <dc:creator>GrumpyOldMen</dc:creator>
    <dc:date>2018-11-22T16:53:25Z</dc:date>
    <item>
      <title>Query Not Zeroed disks</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Query-Not-Zeroed-disks/m-p/144807#M32131</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;After destroying the aggr we could see disks will be part of spare disks with not zeroed.&lt;/P&gt;
&lt;P&gt;RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)&lt;BR /&gt;--------- ------ ------------- ---- ---- ---- ----- -------------- --------------&lt;BR /&gt;Spare disks for block checksum&lt;BR /&gt;spare v5.25 v5 ? ? FC:B 0 FCAL 15000 1020/2089984 1027/2104448 (not zeroed)&lt;BR /&gt;spare v5.26 v5 ? ? FC:B 0 FCAL 15000 1020/2089984 1027/2104448 (not zeroed)&lt;BR /&gt;spare v5.27 v5 ? ? FC:B 0 FCAL 15000 1020/2089984 1027/2104448 (not zeroed)&lt;BR /&gt;spare v5.28 v5 ? ? FC:B 0 FCAL 15000 1020/2089984 1027/2104448&lt;BR /&gt;spare v5.29 v5 ? ? FC:B 0 FCAL 15000 1020/2089984 1027/2104448&lt;BR /&gt;spare v5.32 v5 ? ? FC:B 0 FCAL 15000 1020/2089984 1027/2104448&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Questions is why disks are showing as not zeroed?&lt;/P&gt;
&lt;P&gt;Was there any information available on the destroyed aggr?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;SEENIKANNAN&lt;/P&gt;
&lt;P&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;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 13:06:06 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Query-Not-Zeroed-disks/m-p/144807#M32131</guid>
      <dc:creator>SEENIKANNAN</dc:creator>
      <dc:date>2025-06-04T13:06:06Z</dc:date>
    </item>
    <item>
      <title>Re: Query Not Zeroed disks</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Query-Not-Zeroed-disks/m-p/144835#M32139</link>
      <description>&lt;P&gt;I guess that, when you destroy an aggregate, the data that is still there is not really erased but made unavailable for access.&amp;nbsp;&amp;nbsp;When you really want that the disks do not contain any data when the storage is end of use, you have to sanitize disks....&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Spare disks can be added to an aggregate, can be used for creating a new one.... But in all cases the disks must contain only zeros. Adding zeros does not affect parity calculation. So that way we can hot-add disks,that's why zeroing is needed.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 22 Nov 2018 16:53:25 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Query-Not-Zeroed-disks/m-p/144835#M32139</guid>
      <dc:creator>GrumpyOldMen</dc:creator>
      <dc:date>2018-11-22T16:53:25Z</dc:date>
    </item>
  </channel>
</rss>

