topic Please Help With this in Active IQ Unified Manager Discussions

Please Help With this

lewisdebrah — Thu, 05 Jun 2025 06:51:32 GMT

We have currently configured one NetApp node as per below:

- Active/Active Failover Cluster (since ther are two controllers per each)

- One Controller-B of the two is the Owner of 11 disk (12 available) and one left for the other Controller-A

- For Controller-B, 3 disk used by default for the system data and configuration (1 disk for data and 2 disk for parity, RaidDp). On this resides aggregate0 (aggr0) and volume0(vol0).

- Still on controller-B, we have created a aggregate1 (aggr1) thus; 1 disk for parity, 1 for spare, and 6 is available for the actual storage capacity. This is for Raid4.

- It should be noted that the actual disk capacity used for the configuration is 79GB less than the actual size of 547GB that the System sees. Therefore, for the 6 disks the actual, the actual size useable = 468 * 6 = 2808GB = 2.74TB. Is this based on the techno

logy of the NetApp Device.

- One disk is used by Controller-A for its default system root configuration (it does not have a spare which is even not advisable). Is this also ok? Because we need more storage space of about 4TB. What will be the best Configuration to achieve this or higher?

In order to achieve the expected drive size, we will need your prompt advice.

Re: Please Help With this

aborzenkov — Fri, 01 Jul 2011 04:36:19 GMT

No, this configuration is not OK. Running NetApp system with a single disk is not likely to be supported. You need at least two for RAID protection.

Please check knowledge base article 3011274 which contains detailed description about NetApp is using disk space.

Please Help With this

eric_barlier — Fri, 01 Jul 2011 09:12:20 GMT

prompt reply? this is a forum, we all already have jobs and contributing here is purely volontary.

With respect to your problem. As mentioned you cannot have 1 disk on one controller. the least amount you can have

is 2 for a raid4 aggr. to accomodate a root volume.

On the smaller controllers (such as a 2020) its a common trade off to only have 1 aggregate and as you will get more available space given that you dont need parity disks for a new aggregate.

What I would do is use aggr0 for all data but NEVER EVER put any data in vol0. So dont share it out, dont export it out.

This is how I would do your setup

controller 1:

aggr0 1 data disk, 2 disks for raid_dp

conroller 2:

aggr0 raid4, 1 data disk, 1 raid4 disk.

The rest of the disks can be used for data on controller 1. Make sure your RG size is default size and can accomodate ALL disks.

You could maybe even spare a disk for controller 2 and have it use raid_dp if you end up with enough space.

Cheers,

Eric

Re: Please Help With this

Darkstar — Wed, 06 Jul 2011 12:24:45 GMT

eric.barlier wrote:

With respect to your problem. As mentioned you cannot have 1 disk on one controller. the least amount you can have

is 2 for a raid4 aggr. to accomodate a root volume.

Just some nitpicking, it is perfectly possible from a technical point of view to have a single-disk root aggregate. However this is not documented, not supported and *will* get you into trouble if you try and open up a support case 😉

netapp10> sysconfig -r

Aggregate aggr0 (online, raid0) (block checksums)

Plex /aggr0/plex0 (online, normal, active, pool0)

RAID group /aggr0/plex0/rg0 (normal)

RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)

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

data 0c.00.2 0c 0 2 SA:B 0 SATA 7200 423111/866531584 423946/868242816

Pool1 spare disks (empty)

Pool0 spare disks (empty)

Partner disks

RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)

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

partner 0c.00.3 0c 0 3 SA:B 0 SATA 7200 0/0 423946/868242816

partner 0c.00.6 0c 0 6 SA:B 0 SATA 7200 0/0 423946/868242816

partner 0c.00.0 0c 0 0 SA:B 0 SATA 7200 0/0 423946/868242816

partner 0c.00.1 0c 0 1 SA:B 0 SATA 7200 0/0 423946/868242816

partner 0c.00.7 0c 0 7 SA:B 0 SATA 7200 0/0 423946/868242816

partner 0c.00.5 0c 0 5 SA:B 0 SATA 7200 0/0 423946/868242816

partner 0c.00.4 0c 0 4 SA:B 0 SATA 7200 0/0 423946/868242816