Display spare disks
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.
Disks with the same disk-class value are compatible for use in the same aggregate.
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.
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.
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.
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.
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.
When disks are zeroed, they can be provisioned directly into aggregates which avoids a lengthy zeroing process.
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.
Disk offline events are typically temporary events which allow Data ONTAP to perform background error recovery activity.
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.
Disks are left behind if they are not responding during a giveback or switchback event.
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.
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.
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.
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.
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 zeroedCheck 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.