<?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: Reallocate on Snaplock aggregate after disk addition in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Reallocate-on-Snaplock-aggregate-after-disk-addition/m-p/14934#M3400</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;To my knowledge its never been best practice to add a couple of disks at the time. for the exact reason you mention; avoid hot spots. &lt;/P&gt;&lt;P&gt;Add many disks and you ll be fine. i know this answer does not sit well with those that pay the bill for the disks but hey... thats the answer&lt;/P&gt;&lt;P&gt;anyways to avoid degraded performance. &lt;SPAN __jive_emoticon_name="wink" __jive_macro_name="emoticon" class="jive_macro jive_macro_emoticon jive_emote" src="https://community.netapp.com/5.0.1/images/emoticons/wink.gif"&gt;&lt;/SPAN&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 16 Nov 2011 15:39:20 GMT</pubDate>
    <dc:creator>ERIC_TSYS</dc:creator>
    <dc:date>2011-11-16T15:39:20Z</dc:date>
    <item>
      <title>Reallocate on Snaplock aggregate after disk addition</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Reallocate-on-Snaplock-aggregate-after-disk-addition/m-p/14915#M3394</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are expanding our Snaplocked aggregates by a couple of disks, and are trying to avoid creating "hot disks".&lt;/P&gt;&lt;P&gt;Can you run reallocate on Snaplock aggregates? Would there be any benefits?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think it would be similar to running reallocate on volumes with snapshots, which means very little benefits. Has anyone&lt;/P&gt;&lt;P&gt;done this and seen results?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:27:53 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Reallocate-on-Snaplock-aggregate-after-disk-addition/m-p/14915#M3394</guid>
      <dc:creator>fabian213</dc:creator>
      <dc:date>2025-06-05T07:27:53Z</dc:date>
    </item>
    <item>
      <title>Re: Reallocate on Snaplock aggregate after disk addition</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Reallocate-on-Snaplock-aggregate-after-disk-addition/m-p/14920#M3396</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey Fabian,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(I cannot comment on the Snaplock part)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have worked on filers which were under tremendous load, and every once of performance we could squeeze out of them was important.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes I have done WAFL reallocate on Trad Vols in the old days, which are essentially what AGGR's are today.&lt;/P&gt;&lt;P&gt;Yes I have seen performance improvement and the elimination of "hot disks", I would recommend it based on the following constraints.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; You always will have a chance of data loss running this command, so make sure your management is aware of this factor. (backups, risk mitigation, etc)&lt;/P&gt;&lt;P&gt;2.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; You really need the faster performance for the environment, vs a like too have.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anthony Feigl&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 May 2009 16:16:55 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Reallocate-on-Snaplock-aggregate-after-disk-addition/m-p/14920#M3396</guid>
      <dc:creator>anthonyfeigl</dc:creator>
      <dc:date>2009-05-28T16:16:55Z</dc:date>
    </item>
    <item>
      <title>Re: Reallocate on Snaplock aggregate after disk addition</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Reallocate-on-Snaplock-aggregate-after-disk-addition/m-p/14926#M3398</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey Anthony,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We currently have reallocate scheduled and running on all our volumes that don't contain Snapshots.&lt;/P&gt;&lt;P&gt;I see the improvements on these specific volumes, but with Snaplock, we are unsure if we can&lt;/P&gt;&lt;P&gt;eliminate these hot disks. I've searched the NOW site and have found nothing. Are you aware of any&lt;/P&gt;&lt;P&gt;documentation detailing reallocate on snaplock volumes/aggregates?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the help&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 May 2009 16:26:46 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Reallocate-on-Snaplock-aggregate-after-disk-addition/m-p/14926#M3398</guid>
      <dc:creator>fabian213</dc:creator>
      <dc:date>2009-05-28T16:26:46Z</dc:date>
    </item>
    <item>
      <title>Re: Reallocate on Snaplock aggregate after disk addition</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Reallocate-on-Snaplock-aggregate-after-disk-addition/m-p/14929#M3399</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Fabian,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Currently the reallocate command isn't supported on SnapLock aggregates.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;S.Naresh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Nov 2011 09:23:01 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Reallocate-on-Snaplock-aggregate-after-disk-addition/m-p/14929#M3399</guid>
      <dc:creator>nareshs</dc:creator>
      <dc:date>2011-11-16T09:23:01Z</dc:date>
    </item>
    <item>
      <title>Re: Reallocate on Snaplock aggregate after disk addition</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Reallocate-on-Snaplock-aggregate-after-disk-addition/m-p/14934#M3400</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;To my knowledge its never been best practice to add a couple of disks at the time. for the exact reason you mention; avoid hot spots. &lt;/P&gt;&lt;P&gt;Add many disks and you ll be fine. i know this answer does not sit well with those that pay the bill for the disks but hey... thats the answer&lt;/P&gt;&lt;P&gt;anyways to avoid degraded performance. &lt;SPAN __jive_emoticon_name="wink" __jive_macro_name="emoticon" class="jive_macro jive_macro_emoticon jive_emote" src="https://community.netapp.com/5.0.1/images/emoticons/wink.gif"&gt;&lt;/SPAN&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Nov 2011 15:39:20 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Reallocate-on-Snaplock-aggregate-after-disk-addition/m-p/14934#M3400</guid>
      <dc:creator>ERIC_TSYS</dc:creator>
      <dc:date>2011-11-16T15:39:20Z</dc:date>
    </item>
  </channel>
</rss>

