topic Re: Semi-Nube FAS2020 Capacity issue in ONTAP Hardware

Semi-Nube FAS2020 Capacity issue

mvetteplex — Thu, 05 Jun 2025 07:19:04 GMT

We have a Fas2020 ,that has 9 207GB drives in an aggregate configuration, Properties show type traditional, online, raid_dp. The system showed that 85% of the drive is used and we had 4 spares so we added two of the spares to the configuration. The total capacity before adding the two drives was listed as 592 GB and after adding the drives is still listed as 592 GB. So doing remedial math, we have 9 200 GB drives that should = 1.8TB of space I know that two of the drives are being used for Parity so we are now @ 1.4 TB.

The big question is whay are we missing 800GB of sapce and why adding two drives didn't change the space available.

I "lucked" into helping with this system and need ll of the hlp I can get.

Thanks Mike

Re: Semi-Nube FAS2020 Capacity issue

lwei — Fri, 29 Jan 2010 22:14:47 GMT

Hi Mike,

Did you expand the RAID-DP group size before adding the two drives? If not, it may add a new group in the aggregate and the two new drives become parity drives.

How much space is reserved by the aggregate and/or volume(s)? That might explain the difference.

Thanks,

Wei

Re: Semi-Nube FAS2020 Capacity issue

mvetteplex — Mon, 01 Feb 2010 16:48:33 GMT

lwie,

Thanks, that at least gives me a direction to look, no we didn't expand the raid-dp before we added the new, it also doesn't look like it made a new group, here is what I see:

aggr status -r
Aggregate vol1 (online, raid_dp) (block checksums)
Plex /vol1/plex0 (online, normal, active)
RAID group /vol1/plex0/rg0 (normal)

      RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks)    Phys (MB/blks)
      --------- ------ ------------- ---- ---- ---- ----- --------------    --------------
      dparity   0b.19   0b    1   3   FC:B   - ATA   7200 211377/432901760 211921/434014304
      parity    0a.20   0a    1   4   FC:A   - ATA   7200 211377/432901760 211921/434014304
      data      0b.21   0b    1   5   FC:B   - ATA   7200 211377/432901760 211921/434014304
      data      0a.22   0a    1   6   FC:A   - ATA   7200 211377/432901760 211921/434014304
      data      0a.23   0a    1   7   FC:A   - ATA   7200 211377/432901760 211921/434014304
      data      0a.24   0a    1   8   FC:A   - ATA   7200 211377/432901760 211921/434014304
      data      0b.29   0b    1   13 FC:B   - ATA   7200 211377/432901760 211921/434014304
      data      0a.27   0a    1   11 FC:A   - ATA   7200 211377/432901760 211921/434014304
      data      0b.25   0b    1   9   FC:B   - ATA   7200 211377/432901760 211921/434014304

Thanks for the input!

Re: Semi-Nube FAS2020 Capacity issue

lwei — Mon, 01 Feb 2010 18:19:07 GMT

You can check the RAID group size, expand it, then add the two disks:

>aggr status -r // check for raidsize

>aggr options aggr1 raidsize 16 // set aggr1 raidsize to 16

>aggr add aggr1 2 // add 2 disks to aggr1

Thanks,

Wei

Re: Semi-Nube FAS2020 Capacity issue

mvetteplex — Mon, 01 Feb 2010 18:57:00 GMT

Actually the aggr status -r does show the added drives so all added "correctly" according to what we can see, the real problem is after adding the drives the space doesn't appear, it still shows only 592 GB of space and 85% of that is used, so it appears that 4 of the drives aren't getting into the allocation pool?

Re: Semi-Nube FAS2020 Capacity issue

lwei — Mon, 01 Feb 2010 23:39:22 GMT

Try aggr show_space an/or df -g -A to see where the space went. -Wei