HP Array Configuration Utility User Guide (416146-001, January 2006)

Using the Command Line Interface 53
Syntax:
<target> add spares=[#:]#:#,[#:]#:#,[#:]#:#–[#:]#:#,...|allunassigned
[forced]
<target> remove spares=[#:]#:#,[#:]#:#,[#:]#:#–[#:]#:#,...|all
where <target> is an array. If the array contains only one logical drive, the logical drive can also be
the target. The parameter forced represses warning message prompts.
Example commands:
=> ctrl slot=3 array B add spares=1:6
=> ctrl slot=4 array all add spares=1:5,1:7
=> ctrl slot=5 array A add spares=1:1–1:5
=> ctrl slot=5 array A remove spares=1:1–1:5
Migrating a logical drive
This command enables you to adjust the stripe size (data block size) or RAID level of a selected logical
drive. For information about selecting an appropriate stripe size or RAID level, refer to the tables in the
"Creating a logical drive (on page 17)" and "Selecting a RAID method (on page 67)" sections.
Consider the following factors before performing a migration:
• For some RAID-level migrations to be possible, you might need to add one or more drives to the
array.
• For migration to a larger stripe size to be possible, the array might need to contain unused drive
space. This extra space is necessary because some of the larger data stripes in the migrated array
are likely to be inefficiently filled.
IMPORTANT: An array expansion, logical drive extension, or logical drive migration takes about 15
minutes per gigabyte, or considerably longer if the controller does not have a battery-backed cache. While
this process is occurring, no other expansion, extension, or migration can occur simultaneously on the same
controller.
Syntax:
<target> modify [raid=0|1+0|1|5|6|adg|?]
[ss=8|16|32|64|128|256|default|?]
where <target> is a logical drive.
The following limitations apply to this command:
• You cannot simultaneously query the RAID level and the stripe size of any given logical drive.
• If you do not specify a RAID level for a query or migration, the CLI uses the existing value by default.
• If you do not specify a stripe size, the CLI uses the default stripe size value for the RAID level that you
specify.
Example commands:
=> ctrl slot=3 ld 1 modify raid=1
=> ctrl slot=4 ld 2 modify ss=16
=> ctrl slot=2 ld 3 modify raid=5 ss=16
Changing the Rebuild Priority setting
The Rebuild Priority setting determines the urgency with which the controller treats an internal command to
rebuild a failed logical drive.
• At the low setting, normal system operations take priority over a rebuild.