Skip to main content
A newer release of this product is available.

storage aggregate show-spare-disks

Contributors
Suggest changes
PDFs

Display spare disks

Availability: This command is available to cluster administrators at the admin privilege level.

Description

The command storage aggregate show-spare-disks displays information about spare disks. The command output depends on the parameter or parameters specified with the command. If no parameters are specified, the command displays information about all spare disks in the cluster.

Parameters

{ [-fields <fieldname>,…​]

If you specify the -fields <fieldname>, …​ parameter, the command output also includes the specified field or fields. You can use '-fields ?' to display the fields to specify.

| [-partition-info ] (privilege: advanced)

Displays the following information about root-data and root-data1-data2 partitioned spares.

  • Disk

  • Type

  • Class

  • RPM

  • Checksum

  • Local Data Usable

  • Local Data1 Usable

  • Local Data2 Usable

  • Local Root Usable

  • Physical Size

  • Status

| [-instance ] }

If this parameter is specified, the command displays detailed information about each spare disk.

[-original-owner <text>] - Original Owner

Selects the spare disks that match this parameter value.

[-disk <disk path name>] - Disk Name

Selects the spare disks that match this parameter value.

[-checksum-style {advanced_zoned | block | none}] - Checksum Style

Selects the spare disks that match this parameter value. Possible values are:

  • block — Supports block checksum

  • advanced_zoned — Supports advanced zone checksum

  • none — No checksum support

[-disk-type {ATA | BSAS | FCAL | FSAS | LUN | MSATA | SAS | SSD | VMDISK | SSD-NVM}] - Disk Type

Selects the spare disks that match this parameter value.

[-effective-disk-type {ATA | BSAS | FCAL | FSAS | LUN | MSATA | SAS | SSD | VMDISK | SSD-NVM}] - Effective Disk Type

Selects the spare disks that match this parameter value.

Hard disk drives with the same effective-disk-type value may be mixed together in the same aggregate depending upon the system's raid.mix.hdd.disktype.capacity and raid.mix.hdd.disktype.performance option settings. Solid state drives with the same effective-disk-type value may be mixed together in the same aggregate depending upon the system's raid.mix.disktype.solid_state option setting.

[-standard-disk-type {SATA | FC | NL-SAS | LUN | SAS | SCSI | SSD | VM-DISK | NVMe-SSD}] - Standard Disk Type

Selects the spare disks that match this parameter value.

[-disk-class {capacity | performance | archive | solid-state | array | virtual}] - Disk Class

Selects the spare disks that match this parameter value. Possible values are:

  • capacity — Capacity-oriented, near-line disk types. Includes disk types FSAS, BSAS and ATA.

  • performance — Performance-oriented, enterprise class disk types. Includes disk types FCAL and SAS.

  • archive — Archive class SATA disks in multi-disk carrier storage shelves. Includes disk type MSATA.

  • solid-state — Solid-state drives. Includes disk type SSD and SSD-NVM.

  • array — Logical storage devices backed by storage arrays and used by Data ONTAP as disks. Includes disk type LUN.

  • virtual — Virtual disks that are formatted and managed by the hypervisor. Includes disk type VMDISK.

Disks with the same disk-class value are compatible for use in the same aggregate.

[-disk-rpm <integer>] - Disk RPM

Selects the spare disks that match this parameter value.

[-effective-disk-rpm <integer>] - Effective Disk RPM

Selects the spare disks that match this parameter value.

Hard disk drives with the same effective-disk-rpm value may be mixed together in the same aggregate depending upon the system's raid.mix.hdd.rpm.capacity and raid.mix.hdd.rpm.performance option settings.

[-syncmirror-pool <text>] - Pool Number

Selects the spare disks that match this parameter value.

[-owner-name {<nodename>|local}] - Current Owner

Selects the spare disks that match this parameter value.

[-home-owner-name {<nodename>|local}] - Home Owner

Selects the spare disks that match this parameter value.

[-dr-owner-name {<nodename>|local}] - DR Home Owner

Selects the spare disks that match this parameter value.

[-usable-size-blks <integer>] - Disk Usable Size in 4K blocks

Selects the spare disks that match this parameter value.

[-local-usable-data-size-blks <integer>] - Local Node Data Usable Size in 4K blocks

Selects the spare disks that match this parameter value.

Disks that have two partitions can be used for one root aggregate and one data aggregate.

Disks that have three partitions can be used for one root aggregate and one or two data aggregates.

This value describes the data partition size (of root-data partitioned disk) or the combined data1 + data2 partition size (of root-data1-data2 partitioned disk) in 4KB blocks.

[-local-usable-root-size-blks <integer>] - Local Node Root Usable Size in 4K blocks

Selects the spare disks that match this parameter value.

Disks that have two partitions can be used for one root aggregate and one data aggregate.

Disks that have three partitions can be used for one root aggregate and one or two data aggregates.

This value describes the root partition size in 4KB blocks.

[-usable-size {<integer>[KB|MB|GB|TB|PB]}] - Disk Usable Size

Selects the spare disks that match this parameter value.

[-total-size {<integer>[KB|MB|GB|TB|PB]}] - Total Size

Selects the spare disks that match this parameter value.

[-local-usable-data-size {<integer>[KB|MB|GB|TB|PB]}] - Local Node Data Usable Size

Selects the spare disks that match this parameter value.

Disks that have two partitions can be used for one root aggregate and one data aggregate.

Disks that have three partitions can be used for one root aggregate and one or two data aggregates.

This value describes the data partition size (of root-data partitioned disk) or the combined data1 + data2 partition size (of root-data1-data2 partitioned disk) in auto-scaled units.

[-local-usable-root-size {<integer>[KB|MB|GB|TB|PB]}] - Local Node Root Usable Size

Selects the spare disks that match this parameter value.

Disks that have two partitions can be used for one root aggregate and one data aggregate.

Disks that have three partitions can be used for one root aggregate and one or two data aggregates.

This value describes the root partition size in auto-scaled units.

[-is-disk-zeroed {true|false}] - Is Disk Zeroed?

Selects the spare disks that match this parameter value.

When disks are zeroed, they can be provisioned directly into aggregates which avoids a lengthy zeroing process.

[-is-disk-zeroing {true|false}] - Is Disk Zeroing?

Selects the spare disks that match this parameter value.

[-zeroing-percent <percent>] - Zeroing Percentage Completed

Selects the spare disks that match this parameter value.

[-is-sparecore {true|false}] - Sparecore Disk?

Selects the spare disks that match this parameter value.

[-sparecore-status <Spare core status>] - Sparecore Status

Selects the spare disks that match this parameter value.

[-sparecore-percent <percent>] - Sparecore Percentage Completed

Selects the spare disks that match this parameter value.

[-is-disk-shared {true|false}] - Is Disk Shared?

Selects the spare disks that match this parameter value.

Shared disks have partitions that allow them to be used in multiple aggregates and between nodes in an HA pair. When set to true , this parameter selects shared disks in which the root partition and/or the data partition is a spare. When set to false only spare disks without partitions are displayed. When this parameter is not used, all spare disks are displayed.

[-is-disk-offline {true|false}] - Is Disk Offline?

Selects the spare disks that match this parameter value.

Disk offline events are typically temporary events which allow Data ONTAP to perform background error recovery activity.

[-is-disk-sick {true|false}] - Is Disk Sick?

Selects the spare disks that match this parameter value.

A sick disk triggers Rapid RAID Recovery to copy data to a spare drive. At the end of the process the sick disk is marked as broken .

[-is-disk-left-behind {true|false}] - Is Disk Left Behind Spare?

Selects the spare disks that match this parameter value.

Disks are left behind if they are not responding during a giveback or switchback event.

[-local-usable-data1-size-blks <integer>] - Local Node Data1 Usable Size in 4K blocks (privilege: advanced)

Selects the spare disks that match this parameter value.

Disks that have two partitions can be used for one root aggregate and one data aggregate.

Disks that have three partitions can be used for one root aggregate and one or two data aggregates.

This value describes the data1 partition size of a root-data1-data2 partitioned disk in 4KB blocks.

[-local-usable-data2-size-blks <integer>] - Local Node Data2 Usable Size in 4K blocks (privilege: advanced)

Selects the spare disks that match this parameter value.

Disks that have two partitions can be used for one root aggregate and one data aggregate.

Disks that have three partitions can be used for one root aggregate and one or two data aggregates.

This value describes the data2 partition size of a root-data1-data2 partitioned disk in 4KB blocks.

[-local-usable-data1-size {<integer>[KB|MB|GB|TB|PB]}] - Local Node Data1 Usable Size (privilege: advanced)

Selects the spare disks that match this parameter value.

Disks that have two partitions can be used for one root aggregate and one data aggregate.

Disks that have three partitions can be used for one root aggregate and one or two data aggregates.

This value describes the data1 partition size of a root-data1-data2 partitioned disk in auto-scaled units.

[-local-usable-data2-size {<integer>[KB|MB|GB|TB|PB]}] - Local Node Data2 Usable Size (privilege: advanced)

Selects the spare disks that match this parameter value.

Disks that have two partitions can be used for one root aggregate and one data aggregate.

Disks that have three partitions can be used for one root aggregate and one or two data aggregates.

This value describes the data2 partition size of a root-data1-data2 partitioned disk in auto-scaled units.

Examples

Display spare disks owned by node node-b .

cluster1::> storage aggregate show-spare-disks -owner-name node-b

Original Owner: node-b
 Pool0
  Spare Pool
Usable Physical
 Disk             Type  Class          RPM Checksum           Size     Size Status
 ---------------- ----- ----------- ------ -------------- -------- -------- --------
 1.1.13           BSAS  capacity     7200  block           827.7GB  828.0GB zeroed
 1.1.15           BSAS  capacity     7200  block           413.2GB  414.0GB zeroed

Original Owner: node-b
 Pool0
  Partitioned Spares
                                                             Local    Local
                                                              Data     Root Physical
 Disk             Type  Class          RPM Checksum         Usable   Usable     Size Status
 ---------------- ----- ----------- ------ -------------- -------- -------- -------- --------
 1.0.8            SAS   performance  10000 block           472.9GB  73.89GB  547.1GB zeroed

Check on the progress of a previous disk zeroing command.

cluster1::> storage aggregate show-spare-disks -owner-name node-b -zeroing-percent >0

Original Owner: node-b
 Pool0
  Spare Pool
Usable Physical
 Disk             Type  Class          RPM Checksum           Size     Size Status
 ---------------- ----- ----------- ------ -------------- -------- -------- --------
 1.1.13           BSAS  capacity      7200 block           827.7GB  828.0GB zeroing, 17% done
 1.1.15           BSAS  capacity      7200 block           413.2GB  414.0GB zeroing, 28% done
2 entries were displayed.