AFF

AFF-A200 NetApp Release 9.11.1P18 , Possible AFF issue

Cristian_B
127 Views

Hi All,

First of all, thank you for your collaboration.
System:

AFF-A200 NetApp Release 9.11.1P18

 

Customer states after initialization of Netapp system:

Now we are running into the following problem. The NetApp now sees the disks as 1.7TB instead of 3.49TB.

The NetApp has 16 x 3.84TB SSDs but does not see them completely.

 

I have tried various options for initializing the disks but it still sees some disks as 1.7.

Below is what I have tried.

 

First “Clean configuration and initialize all disks” in the boot menu then I get the following.

 

I suspect  cause is AFF system where SSDs are divided into multiple partitions and assigned to multiple owners.

Cristian_B_0-1740475277728.png

 

Please, let me know if you have some solution or action plan to solve this issue.

Thanks in advance

Cristian

1 ACCEPTED SOLUTION

TMACMD
87 Views

There is nothing to fix. This is by design. You actually end up with more capacity. If you did not use adp, then each node “wastes” 3 drives each. You 16 is now 10. Then you mashes in this case let’s say one aggregate after you assign all the drives. You leave one for spare and two are parity. You effectively then use 7 disks for data. 

with adp they are partitioned into 3 parts. A root. A P1 and a P2 which are data partitions

reach nodes will be assigned half the drives and use those root partitions for the root aggregate. 
one node gets all the P1 partitions and the other node gets all the P2 partitions. 
each node may now use up to 16 (15 if you leave a spare) partitions. Much more effective capacity

 

 it does look like someone inserted 7.6t drives into sorts 10 & 11. 

please send the output of

 disk show -fields model

View solution in original post

5 REPLIES 5

AmitKerkar
121 Views

This could be due to initialization with ADP (advanced drive partition)

Hi AmitKerkar,

Thank you for your comment, but how should we solve this issue? We tried to do the following action from "Advanced Drive Partitioning Boot Menu Options" :

"Clean configuration and initialize node with whole disks"

Please, let me know your technical approach 

Thank you

Cristian

TMACMD
88 Views

There is nothing to fix. This is by design. You actually end up with more capacity. If you did not use adp, then each node “wastes” 3 drives each. You 16 is now 10. Then you mashes in this case let’s say one aggregate after you assign all the drives. You leave one for spare and two are parity. You effectively then use 7 disks for data. 

with adp they are partitioned into 3 parts. A root. A P1 and a P2 which are data partitions

reach nodes will be assigned half the drives and use those root partitions for the root aggregate. 
one node gets all the P1 partitions and the other node gets all the P2 partitions. 
each node may now use up to 16 (15 if you leave a spare) partitions. Much more effective capacity

 

 it does look like someone inserted 7.6t drives into sorts 10 & 11. 

please send the output of

 disk show -fields model

Hi TMACMD,

Thank you for your detailed comment, please, you can see below the command output requeseted:

All SSDs are 3.84Tb.

00.0 :  NETAPP   X357_S163A3T8ATE NA54 3662.5GB 520B/sect (S394NA0HB10778)

                00.1 :  NETAPP   X357_S163A3T8ATE NA54 3662.5GB 520B/sect (S394NA0HB10781)

                00.2 :  NETAPP   X357_S16433T8ATE NA55 3662.5GB 520B/sect (S3SGNF0K802712)

                00.3 :  NETAPP   X357_S163A3T8ATE NA54 3662.5GB 520B/sect (S394NA0HB10526)

                00.4 :  NETAPP   X357_S163A3T8ATE NA54 3662.5GB 520B/sect (S394NA0J312466)

                00.5 :  NETAPP   X357_S163A3T8ATE NA54 3662.5GB 520B/sect (S394NA0J312622)

                00.6 :  NETAPP   X357_S163A3T8ATE NA54 3662.5GB 520B/sect (S394NA0HB28373)

                00.7 :  NETAPP   X357_S163A3T8ATE NA54 3662.5GB 520B/sect (S394NA0HB10788)

                00.8 :  NETAPP   X357_S163A3T8ATE NA54 3662.5GB 520B/sect (S394NA0HB10530)

                00.9 :  NETAPP   X357_S163A3T8ATE NA54 3662.5GB 520B/sect (S394NA0HB10495)

                00.10: NETAPP   X357_S163A3T8ATE NA54 3662.5GB 520B/sect (S394NA0HB10749)

                00.11: NETAPP   X357_S163A3T8ATE NA54 3662.5GB 520B/sect (S394NA0HB10783)

                00.12: NETAPP   X357_S163A3T8ATE NA54 3662.5GB 520B/sect (S394NA0HB10777)

                00.13: NETAPP   X357_S163A3T8ATE NA54 3662.5GB 520B/sect (S394NA0HB10754)

                00.14: NETAPP   X357_S163A3T8ATE NA54 3662.5GB 520B/sect (S394NA0HB28375)

                00.15: NETAPP   X357_S163A3T8ATE NA54 3662.5GB 520B/sect (S394NA0HB28235)

Thank you,
Regards,

Cristian

There's a nice diagram concerning root-data-data (ADPv2) partitioning here:
https://docs.netapp.com/us-en/ontap/concepts/root-data-partitioning-concept.html

Public