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

storage disk replace

Contributors
Suggest changes
PDFs

Initiate or stop replacing a file-system disk

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

Description

The storage disk replace command starts or stops the replacement of a file system disk with spare disk. When you start a replacement, Rapid RAID Recovery begins copying data from the specified file system disk to a spare disk. When the process is complete, the spare disk becomes the active file system disk and the file system disk becomes a spare disk. If you stop a replacement, the data copy is halted, and the file system disk and spare disk retain their initial roles.

Parameters

-disk <disk path name> - Disk Name

This specifies the file system disk that is to be replaced. Disk names take one of the following forms:

  • Disks are named in the form <stack-id> .<shelf> .<bay>

  • Disks on multi-disk carriers are named in the form <stack-id> .<shelf> .<bay> .<lun>

  • Virtual disks are named in the form <prefix>.<number>, where prefix is the storage array's prefix and number is a unique ascending number.

Disk names take one of the following forms on clusters that are not yet fully upgraded to Data ONTAP 8.3:

  • Disks that are not attached to a switch are named in the form <node> :<host_adapter> .<loop_ID> . For disks with a LUN, the form is <node> :<host_adapter> .<loop_ID> L<LUN> . For instance, disk number 16 on host adapter 1a on a node named node0a is named node0a:1a.16. The same disk on LUN lun0 is named node0a:1a.16Llun0.

  • Disks that are attached to a switch are named in the form <node> :<switch_name> :<switch_port> .<loop_ID> . For disks with a LUN, the form is <node> :<switch_name> :<switch_port> .<loop_ID> L<LUN> . For instance, disk number 08 on port 11 of switch fc1 on a node named node0a is named node0a:fc1:11.08. The same disk on LUN lun1 is named node0a:fc1:11.08Llun1.

Before the cluster is upgraded to Data ONTAP 8.3, the same disk can have multiple disk names, depending on how the disk is connected. For example, a disk known to a node named alpha as alpha:1a.19 can be known to a node named beta as beta:0b.37. All names are listed in the output of queries and are equally valid. To determine a disk's unique identity, run a detailed query and look for the disk's universal unique identifier (UUID) or serial number.

-action {start | stop} - Action

This specifies whether to start or stop the replacement process.

[-replacement <disk path name>] - Replacement

This specifies the spare disk that is to replace the file system disk.

[-allow-same-carrier <true>] - Allow Same RAID Group Within Carrier

This parameter can be used to allow two disks housed in the same carrier to be in the same RAID group when you replace a disk in an aggregate.

Having disks in the same carrier in the same RAID group is not desirable because a carrier failure can cause a simultaneous outage for two disks in the same RAID group. You can replace a disk in an aggregate with a disk that causes this situation, but when an alternate disk becomes available, Data ONTAP automatically initiates a series of disk copy operations to put the disks into different RAID groups. For this reason, you should use this parameter only when necessary. When possible, ensure that disks housed in the same carrier are in different RAID groups.

This parameter affects only the disk replace operation. It is not a persistent attribute of the aggregate.

[-m, -allow-mixing <true>] - Allow Mixing of Disks of Different RPM or Pool

This optional parameter specifies whether the disk can be replaced with another disk of different RPM or from different Pool. This parameter affects only the current disk replacement operation.

Examples

The following example begins replacing a file system disk named 1.0.16 with a spare disk named 1.1.14 .

cluster1::> storage disk replace -disk 1.0.16 -replacement 1.1.14 -action start