root-data-data2 aggregate setup

[William365]

Hi,

We have one SSD shelf with 24 disk configure with root-data-data2.  I want to create an aggregate using 23 disk leaving one for spare,  is the the optimal way to use the data partition space?

cluster1::> aggr create -aggregate aggr_ssd1 -diskcount 23 -raidtype raid_dp -node cluster1-01 -disktype ssd

Two other questions are: what are the two SSD drives with 23.39GB (Local Root Usable) mean and why I don't see any spare drive(s) for the root aggregate?

cluster1::> storage aggregate show-spare-disks -disk-type SSD

Original Owner: cluster1-01
Pool0
Root-Data1-Data2 Partitioned Spares
Local Local
Data Root Physical
Disk Type Class RPM Checksum Usable Usable Size Status
---------------- ------ ----------- ------ -------------- -------- -------- -------- --------
1.0.0 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.1 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.2 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.3 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.4 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.5 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.6 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.7 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.8 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.9 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.10 SSD solid-state - block 435.3GB 23.39GB 894.3GB zeroed
1.0.11 SSD solid-state - block 435.3GB 23.39GB 894.3GB zeroed
1.0.12 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.13 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.14 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.15 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.16 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.17 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.18 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.19 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.20 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.21 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.22 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.23 SSD solid-state - block 435.3GB 0B 894.3GB zeroed

Original Owner: cluster1-02
Pool0
Root-Data1-Data2 Partitioned Spares
Local Local
Data Root Physical
Disk Type Class RPM Checksum Usable Usable Size Status
---------------- ------ ----------- ------ -------------- -------- -------- -------- --------
1.0.0 SSD solid-state - block 435.3GB 0B 894.3GB zeroed

Original Owner: cluster1-02
Pool0
Root-Data1-Data2 Partitioned Spares
Local Local
Data Root Physical
Disk Type Class RPM Checksum Usable Usable Size Status
---------------- ------ ----------- ------ -------------- -------- -------- -------- --------
1.0.1 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.2 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.3 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.4 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.5 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.6 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.7 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.8 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.9 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.10 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.11 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.12 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.13 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.14 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.15 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.16 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.17 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.18 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.19 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.20 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.21 SSD solid-state - block 435.3GB 0B 894.3GB zeroed
1.0.22 SSD solid-state - block 435.3GB 23.39GB 894.3GB zeroed
1.0.23 SSD solid-state - block 435.3GB 23.39GB 894.3GB zeroed
48 entries were displayed.

Thank you!

[SpindleNinja · Accepted solution]

Most optimal way is to create an aggr on node1 using partitions from Data1 and a second aggr on node2 using partitions from Data2.   outside of creating a larger aggr, onto will not allow Partitions from the same disk to be in the same raid group.  

Here's a visual of ADPv2 RDD - 

Via here - https://docs.netapp.com/us-en/ontap/concepts/root-data-partitioning-concept.html 

Re: spares - list out the spares,  you'll see where all the root and data spares line up.