NEC Express 5800 Series User Manual page 56

Syntax:
<target> modify size=#|max|? [forced]
where <target> is a logical drive.
If the operating system does not support logical drive extension, carrying out this command makes data on
the logical drive unavailable. Therefore, the CLI displays a warning prompt as a safeguard in case you are
using such an operating system. To prevent the prompt from appearing, use the forced parameter.
Example commands:
=> ctrl slot=3 ld 1 modify size=max
=> ctrl slot=4 ld 1 modify size=?
=> ctrl slot=3 ld 2 modify size=500 forced
Migrating a logical drive
This command enables you to adjust the stripe size (data block size) or RAID level of a selected logical drive.
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 filled inefficiently.
IMPORTANT: An array expansion, logical drive extension, or logical drive migration takes about
15 minutes per gigabyte. While this process is occurring, no other expansion, extension, or
migration can occur simultaneously on the same controller. Controllers that do not support a
battery-backed write cache do not support this process.
Syntax:
<target> modify [raid=0|1+0|1|5|6|50|60|adg|1adm|10adm|?]
[ss=8|16|32|64|128|256|512|1024|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.

At the medium setting, rebuilding occurs for half of the time, and normal system operations occur for
the rest of the time.

At the medium high setting, rebuilding is given a higher priority over normal system operations.

At the high setting, the rebuild takes precedence over all other system operations.
If the logical drive is part of an array that has an online spare, rebuilding begins automatically when drive
SSA CLI 56