Skip to main content
NetApp Knowledge Base

What are the rules for Advanced Disk Partitioning?

Views:
21,592
Visibility:
Public
Votes:
13
Category:
ontap-9
Specialty:
HW
Last Updated:

Applies to

Answer

Topic ADPv1 (root-data) ADPv2 (root-data-data) 
Number of partitions per drive

1 data partition labeled P1

1 root partition labeled P2

2 equal-sized data partitions labeled P1 and P2

1 root partition labeled P3

ONTAP model support

FAS

Refer to the NetApp Hardware Universe for additional information.

AFF and all-SSD FAS systems initialized with ONTAP 9.0 or later will utilize ADPv2 partitioning

Refer to the NetApp Hardware Universe for additional information.

HDD Supported Unsupported
SSD Supported Supported
Maximum drives partitioned at system initialization 24 48
Supported RAID type

RAID-TEC

RAID-DP

RAID-TEC

RAID-DP

RAID4 (ONTAP 9.5 and later)

Partition sizes created at system initialization Refer to NetApp Hardware Universe, select the FAS platform and ONTAP version, and from the result choose the ADP Root Partition Configuration link Refer to NetApp Hardware Universe, select the AFF platform and ONTAP version, and from the result choose the ADP Root Partition Configuration link
Mixing of partitions and whole disks in same RAID group Unsupported Unsupported
Mixing of partitions and whole disks in same aggregate with separate RAID groups for each Supported Supported

Maximum drives allowed to be partitioned in an HA pair

Note: Refer to NetApp Hardware Universe for  platform-specific drive limits

480 in ONTAP 9.14.1 and later

240 in previous ONTAP releases

480 in ONTAP 9.14.1 and later

240 in previous ONTAP releases

Root partition usage Only available to be used for the node root aggregate Only available to be used for the node root aggregate
Using both partitions from single disk in the same aggregate Not applicable Supported, but each partition must be in a unique RAID group
Partition and container (disk) ownership The same node owns the container and the partitions

One node owns the container, root partition, and the first data partition

The HA partner node owns the second data partition

Automatic partitioning support in ONTAP Refer to Why is a newly added disk not auto-partitioned on ADP systems? Refer to Why is a newly added disk not auto-partitioned on ADP systems?
Spare requirements if all aggregates contain RAID groups that use partitions 1 whole HDD available on each node of the HA pair (the disk can be partitioned, but both partitions must be available as spares) 1 whole spare disk per HA pair is required (the spare can be partitioned across the nodes)
Spare requirements if aggregates contain RAID groups with a mix of partitions and whole disks 2 whole spare disks for each node that has both a partitioned disk RAID group and a non-partitioned RAID group 1 whole spare disk per node so that a spare is always available both for the partitioned disk RAID groups and the whole disk RAID groups
Spare requirements overall Refer to Spares Low Resolution guide Refer to Spares Low Resolution guide

NOTE!
ADP v2 is unsupported in mixed SSD/HDD configuration no matter in AFF or FAS platform.

Additional Information

  • The following example error message is reported when attempting to change the RAID type to an unsupported version:

cluster1::> aggr modify -aggregate aggr0 -raidtype raid4

Error: command failed: Failed to modify raidtype of aggregate "aggr0".
Reason: Change to raidtype RAID4 is not supported. Fields that were successfully modified: none

  • NetApp Hardware Universe contains extensive information for each supported platform on initial partition sizes for each supported disk type.
NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.