Hp Smart Storage Administrator Manuel d'utilisateur télécharger pdf (Page 61)

Operations 61

SSD Over Provisioning Optimization

Access to solid state devices can be optimized by deallocating all used blocks before any data is written to

the drive. The optimization process is performed when the first logical drive in an array is created, and when

a physical drive is used to replace a failed drive. Not all controllers support this option.

This feature is disabled by default in the CLI.

When creating the first logical drive in an array, the ssdoverprovisioningoptimization parameter

specifies to initialize solid state drives supporting the rapid parity initialization feature. The only valid option

is "on".

Example:

ctrl slot=1 create type=ld drives=1I:1:1 ssdoverprovisioningoptimization=on

ctrl slot=1 create type=ld drives=1I:1:2 ssdopo=on

Assigning a chassis name to the controller

If a controller is configured with at least one logical drive, you can give the controller a simplified name (the

chassis name) to make it easier to identify and enter the correct controller in a command.

Syntax:

<target> modify ch="new chassis name"

where <target> is a controller. If you change the chassis name of a controller that you have set as the

default target ("Setting the target" on page 53), you must reset the target.

Example commands:

=> ctrl sn=P56350D9IP903J modify ch="Lab 6"

=> ctrl ch="Lab 4" modify ch="Lab 6"

Managing spare drives

Assigning one or more online spare drives to an array enables you to postpone replacement of faulty drives.

However, it does not increase the fault-tolerance level of any logical drives in the array. For example, a

logical drive in a RAID 5 configuration suffers irretrievable data loss if two of its physical drives are

simultaneously in a failed state, regardless of the number of spare drives assigned to the array.

Any drive that you want to use as a spare must meet the following criteria:

• It must be an unassigned drive or a spare for another array.

• It must be of the same type as existing drives in the array (for example, SATA or SAS).

• It must have a capacity no less than that of the smallest drive in the array.

Syntax:

<target> add spares=[#:]#:#,[#:]#:#,[#:]#:#–[#:]#:#,...|allunassigned

[forced]

<target> remove spares=[#:]#:#,[#:]#:#,[#:]#:#–[#:]#:#,...|all

where <target> is an array (or logical drive, if the array contains only one logical drive). The forced

parameter represses any warning message prompts. If you specify a drive range, any drives in the range that

do not meet the previous criteria are not used.

Example commands:

=> ctrl slot=3 array B add spares=1:6

1 2 ... 56 57 58 59 60 61 62 63 64 65 66 ... 126 127

Pas de commentaire

Hp Smart Storage Administrator Manuel d'utilisateur Page 61