nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

AFF Partitioning in 9.1

coreywanless

I had such good luck with my last post. I'm going for 2 for 2. 😄

Current Ontap 9 Documentation states that in an AFF, you should assign disks 0-11 to node 1 and 12-24 to node 2.

https://library.netapp.com/ecm/ecm_download_file/ECMLP2495116 (PG 😎

However, I see that we now have 2 data partitions:

xxxxx::*> disk partition show 9.0.1.*

Usable Container Container

Partition Size Type Name Owner

------------------------- ------- ------------- ----------------- -----------------

9.0.1.P1 1.72TB spare Pool0 xxxxx

9.0.1.P2 1.72TB spare Pool0 xxxxx

9.0.1.P3 59.72GB aggregate /xxxrootxxx/plex0/rg0

xxxxx

Should the new best practice be to assign all P1's to node 1 and all P2's to node 2?

Looking for some guidance.

Thanks in advance!

Find more posts tagged with

FAS

Accepted answers

dirk_ecker

That is correct.

Root-Data-Data (R-D2) partitioning divides SSDs into 2 large data partitions and 1 small root partition. One data partition per SSD is assigned to each node in the HA pair.

Only one SSD is required for hot spare partitions. This results in more usable capacity.

You then create an aggregate with a raid size of 23 (21 data + 2 parity) on each node.

I hope this helps!

All comments

dirk_ecker

That is correct.

Root-Data-Data (R-D2) partitioning divides SSDs into 2 large data partitions and 1 small root partition. One data partition per SSD is assigned to each node in the HA pair.

Only one SSD is required for hot spare partitions. This results in more usable capacity.

You then create an aggregate with a raid size of 23 (21 data + 2 parity) on each node.

I hope this helps!

andris

The extra data partition in the root-data-data version doesn't really change the disk assignment guidance for the physical (container) disks in an AFF system. We're still say saying half of the shelf is owned by node 1 and the other half is owned by node 2.

See step 9 in this KB:

https://kb.netapp.com/support/s/article/ka31A00000012lQ/How-to-convert-or-initialize-a-system-for-Root-Data-Data-Partitioning

davidrnexon

Hi Andris, the KB article seems to talk about the advanced disk partitioning with 2 partitions, not the newer enahnced ADP 3 partition layout. I've been looking for some more documentation on the 3 partition layout but can't find any links or sections in the 9.1 documentation. Would you have a KB or documentation link for it ?

andris

That's the right KB...

root-data-data = 3 partitions.

Only AFF systems running 9.0+ are supported for root-data-data partitioning.

davidrnexon

Is best practice for 3 partitions root+data+data assigned to the same node, or would you assign 1 data partition to the HA partner, or doesn't it matter ?

FYI - I'm enquiring about A300's running 9.1

AlexDawson

Hi midi,

Just put them into the empty slots in the two DS2246s attached and they will be automatically partitioned, then it's a matter of assigning the data partitions to existing aggregates using either the GUI or CL
Hope this helps!

midi

Hi everyone,

Thanks for your replies.

LORENZO_CONTI

Hello,

could someone can clarify it there could be some problem having for instance 12 ssd and physical ownership assigned in this way?

0-5 node1

6-11 node2

This is the schema that is used as factory default.

Thank you

andris

I'd need more context to answer your particular question... are you referring to a controller's internal disks? Which model?

Are there 24 bays or 12? Or are you referring to external storage being added (again, 12 or 24 bays)?

What I can say as a general comment that on AFF systems you should lay out drives in partially filled shelves in an "outside in" manner. E.g. If 12 SSD's in a 24-bay shelf, place in 0-5 and 18-23. Option 9b/ADP initialization will automatically assign the container disk ownership of 0-5 to node A and 18-23 to node B. Then, perform root-data-data partitioning.

LORENZO_CONTI

Hello @andris ,

I was thinking to an A-220 with onboard slot. The system is now in production with 0-5 and 6-11 😞