Skip to main content
NetApp Knowledge Base

What sparing criteria does the 'Low number of spare disks' healthcheck use?

Views:
2,448
Visibility:
Public
Votes:
0
Category:
disk-drives
Specialty:
hw
Last Updated:

Applies to

  • All FAS systems
  • All AFF systems

Answer

The drive sparing criteria that the check uses is:

  • Drives are broken up into groups of drive types that can be mixed into raid groups/aggregates and also used as spares for each other:
  • The default value for the raid.disktype.enable option is off, which allows the mixing disk types. What this means is that the following disk types are considered to be equivalent for the purposes of creating and adding to aggregates, and spare management:
  • BSAS, SATA and ATA
  • FCAL and SAS
    • GROUP | [FCAL, SAS] | with the option raid.disktype.enable off or raid.mix.hdd.disktype.performance on
    • GROUP | [ATA, BSAS, SATA,FSAS] | with the option raid.disktype.enable off or raid.mix.hdd.disktype.capacity on
  • With the option raid.disktype.enable on, or raid.mix.hdd.disktype off it disables the mixing of supported drive types.
    • GROUP | FCAL | with the option raid.disktype.enable on or raid.mix.hdd.disktype.performance off
    • GROUP | SAS | with the options raid.disktype.enable on or raid.mix.hdd.disktype.performance off
    • GROUP | ATA | with the option raid.disktype.enable on or raid.mix.hdd.disktype.capacity off
    • GROUP | SATA | with the option raid.disktype.enable on or raid.mix.hdd.disktype.capacity off
  • A larger drive in the right group can be used as a spare for smaller drives.
  • The sparing requirements that the check uses are:
Drives per node of each group  Required spares per node
1 - 100 1
101 - 400 2
401 - 600 3
601+ 4
  • For SSDs the requirements are: 1 full spare SSD OR 1 Spare partition for each partition in use on that node

 

Scan to view the article on your device