#Basic questions 2 X FAS2552 on a DS2246 (24 disks)

1 messages · Page 1 of 1 (latest)

chilly knoll
#

Hello again folks,

Several questions. I am running OnTap 9.8P4 on both nodes.

I have 24 disks total (1.09TB / 10K SAS) in one shelf DS2246

Correct me if I'm wrong when I elaborate so I can learn properly.
I am looking for the best scenario in my case before ongoing with vservers, volumes etc.
Question #1

On picture 1 we have root aggregate on genesis-01 (10 disks) and genesis-02 (10 disks)

I was wondering can I create a new aggregate on 24 disks (system won't let me) I can only do it on 12 disks. Local Tiers on Ontap GUI creates 2 aggregates of 11 disks for a total of 22 disks. I imagine the 2 others will be spare. But at the moment they shared.

**Question #2 **

Still on picture 1 I was trying a lot to change the 4 disks (1.0.20-1.0.23) from shared to spare but I am having a hard time finding a solution after some time searching and trying.

Could you please help me out ?

Thank you 🙂 By the way cool channel Nick I am currently watching the ADP video.

chilly knoll
#

Question #3 for FAS2552 can I install the latest ONTAP versions ? 9.12 (example)

vivid dirge
#

For question 3, you can check the maximum supported ONTAP version by looking up your FAS model on our Hardware Universe site @ hwu.netapp.com

chilly knoll
mortal holly
#

for Question 1, yes, but you have to manually reassign the disks to a single node to create one big aggregate

#

for question 2, the disks will stay shared because they are partitioned. the partitions are spare. try set advanced; storage disk partition show

chilly knoll
chilly knoll
mortal holly
red fox
#

try: storage disk create-partition

mortal holly
# red fox try: storage disk create-partition

but he already has the partitions 😉
he needs to reassign them. reassignment of the data partition works with storage disk removeowner -disk ... -data true, followed by storage disk assign -disk ... -data true -owner <node>. After all partitions are reassigned to the same owner, you should be able to create an aggregate using all disks (23 out of the 24, because you still need a spare... make sure to set max-raid-size to at least 23 or you'll end up with a lot less free space than what you expected)

chilly knoll
#

@mortal holly By doing will I still have HA if one node dies ?

chilly knoll
#

I'll give it a try. Thank you sir.

chilly knoll
#

Here's an update.

#

If I try Y after : storage disk removeowner -disk 1.0.0 -data true - apparently the disk is auto-assign so won't affect my changes. Perhaps I'm mistaken

red fox
#

There is an easier way to do this

#

You have 24x drives and each node has 12x data partitions each

#

So, on one node (pick your favorite one) create an aggregate using all 12x of the data partitions on that node.

#

Then, relocate the aggregate to the partner using: storage aggregate relocation start -aggregate [aggr-name] -node [node name owning the 12x partition aggregate] -destination [node name to own the aggregate]

#

this will, in turn, automatically assign all of those partitions to the new, destination node

#

from there, add 11x more partitions into RG0, so that you retain 1x spare for the node holding the aggregate

mortal holly
#

that's actually a pretty smart solution 🙂

#

honestly, the disk assignment (especially in MetroCluster IP) is what makes me want to hurt myself (or the storage system 😉 ) every time I have to do it ...

chilly knoll
#

Yes Scott I agree it's a good solution I'll try that and will let you know. Thanks.

chilly knoll
#

It worked. Now trying to find the commands for the other part

mortal holly
#

first you need to delete one of the aggregates again. then set maxraidsize on the other one to 23 (if you didn't do that already) and add all but one disks to it

chilly knoll
#

Awesome it worked. Now then the spare disk is it ok if genesis-02 owns it or that disk needs to be without owner ?

red fox
#

You should reassign it over to node 1. Since it's a spare, it should be easy to do that.

#

or, you can relocate the aggregate over to node 2 for an even simpler course of action

#

either way, the result is the same

chilly knoll
#

Just letting you know it worked. Thanks Scott !

#

Case closed thank you !