<?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 New AFF-A220 root vol and aggr questions in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/New-AFF-A220-root-vol-and-aggr-questions/m-p/163290#M37328</link>
    <description>&lt;P&gt;I have read a the Netapp documentation and searched many forums for answers to the following questions. I just want to confirm the answers or know if anyone has succeeded in 'getting around' what is r&lt;BR /&gt;ecommended. All of the questions are in relation to the root volumes for our Netapp AFF-A220, 42 ssd disks (894GB), Ontap 9.7. I am looking to maximize available disk space but do not want to potentia&lt;BR /&gt;lly cripple our device by 'cutting corners'.&lt;/P&gt;&lt;P&gt;-It is my understanding that each node requires it's own root volume in order to function properly as that is where the OS for the node is. Just confirming this is the case.&lt;/P&gt;&lt;P&gt;-By default, our device came with each node having a 10 disk root vol raid-dp aggr. This seemed like a huge waste of space so I moved the root vols for each of our nodes to 3 disk aggrs. Is there a pr&lt;BR /&gt;oblem with me doing this? Also, the old root vol documentation allowed for a 2 disk RAID4 aggr. Is this still a viable solution in Ontap 9?&lt;/P&gt;&lt;P&gt;-Netapp does not recommend combining data with root vol aggr. I have seen that the issue is that fixing this aggr will result in downtime and inaccessible data. How likely is there to be a problem tha&lt;BR /&gt;t would trigger such an event? Is it worth the risk to maximize available disk space?&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2025 10:37:26 GMT</pubDate>
    <dc:creator>RickB</dc:creator>
    <dc:date>2025-06-04T10:37:26Z</dc:date>
    <item>
      <title>New AFF-A220 root vol and aggr questions</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/New-AFF-A220-root-vol-and-aggr-questions/m-p/163290#M37328</link>
      <description>&lt;P&gt;I have read a the Netapp documentation and searched many forums for answers to the following questions. I just want to confirm the answers or know if anyone has succeeded in 'getting around' what is r&lt;BR /&gt;ecommended. All of the questions are in relation to the root volumes for our Netapp AFF-A220, 42 ssd disks (894GB), Ontap 9.7. I am looking to maximize available disk space but do not want to potentia&lt;BR /&gt;lly cripple our device by 'cutting corners'.&lt;/P&gt;&lt;P&gt;-It is my understanding that each node requires it's own root volume in order to function properly as that is where the OS for the node is. Just confirming this is the case.&lt;/P&gt;&lt;P&gt;-By default, our device came with each node having a 10 disk root vol raid-dp aggr. This seemed like a huge waste of space so I moved the root vols for each of our nodes to 3 disk aggrs. Is there a pr&lt;BR /&gt;oblem with me doing this? Also, the old root vol documentation allowed for a 2 disk RAID4 aggr. Is this still a viable solution in Ontap 9?&lt;/P&gt;&lt;P&gt;-Netapp does not recommend combining data with root vol aggr. I have seen that the issue is that fixing this aggr will result in downtime and inaccessible data. How likely is there to be a problem tha&lt;BR /&gt;t would trigger such an event? Is it worth the risk to maximize available disk space?&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 10:37:26 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/New-AFF-A220-root-vol-and-aggr-questions/m-p/163290#M37328</guid>
      <dc:creator>RickB</dc:creator>
      <dc:date>2025-06-04T10:37:26Z</dc:date>
    </item>
    <item>
      <title>Re: New AFF-A220 root vol and aggr questions</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/New-AFF-A220-root-vol-and-aggr-questions/m-p/163292#M37330</link>
      <description>&lt;P&gt;&lt;EM&gt;-It is my understanding that each node requires it's own root volume in order to function properly as that is where the OS for the node is. Just confirming this is the case.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;YES&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;-By default, our device came with each node having a 10 disk root vol raid-dp aggr. This seemed like a huge waste of space so I moved the root vols for each of our nodes to 3 disk aggrs. Is there a problem with me doing this? Also, the old root vol documentation allowed for a 2 disk RAID4 aggr. Is this still a viable solution in Ontap 9?&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You will want to keep this array using ADP (Advanced Disk Partitioning)&amp;nbsp;&amp;nbsp;&lt;SPAN&gt;&lt;A href="https://docs.netapp.com/ontap-9/topic/com.netapp.doc.dot-cm-concepts/GUID-B745CFA8-2C4C-47F1-A984-B95D3EBCAAB4.html" target="_blank"&gt;https://docs.netapp.com/ontap-9/topic/com.netapp.doc.dot-cm-concepts/GUID-B745CFA8-2C4C-47F1-A984-B95D3EBCAAB4.html&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There's a min required size for the root aggr too - Can be found in hwu.netapp.com&amp;nbsp; &amp;nbsp;You can also see how the ADP sizing layout is for the root and data/data for the A220 partitions.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;-Netapp does not recommend combining data with root vol aggr. I have seen that the issue is that fixing this aggr will result in downtime and inaccessible data. How likely is there to be a problem that would trigger such an event? Is it worth the risk to maximize available disk space?&lt;/EM&gt;&lt;BR /&gt;&lt;BR /&gt;This is probably from an old KB,&amp;nbsp; you &lt;STRONG&gt;cannot&lt;/STRONG&gt; put data on the root aggr anymore.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://docs.netapp.com/ontap-9/topic/com.netapp.doc.dot-cm-vsmg/GUID-A60F4F83-0034-4DB8-838B-06E9D4BEF9A4.html" target="_blank"&gt;https://docs.netapp.com/ontap-9/topic/com.netapp.doc.dot-cm-vsmg/GUID-A60F4F83-0034-4DB8-838B-06E9D4BEF9A4.html&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 25 Jan 2021 16:12:29 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/New-AFF-A220-root-vol-and-aggr-questions/m-p/163292#M37330</guid>
      <dc:creator>SpindleNinja</dc:creator>
      <dc:date>2021-01-25T16:12:29Z</dc:date>
    </item>
    <item>
      <title>Re: New AFF-A220 root vol and aggr questions</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/New-AFF-A220-root-vol-and-aggr-questions/m-p/163306#M37339</link>
      <description>&lt;P&gt;You're likely looking at partitioned drives, so those 10 devices are slices of larger devices. ADP is the most efficient way to carve up your SSDs.&lt;/P&gt;</description>
      <pubDate>Mon, 25 Jan 2021 19:43:19 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/New-AFF-A220-root-vol-and-aggr-questions/m-p/163306#M37339</guid>
      <dc:creator>CHRISMAKI</dc:creator>
      <dc:date>2021-01-25T19:43:19Z</dc:date>
    </item>
  </channel>
</rss>

