CLI Guide

● All disks in a disk group must be the same type (enterprise SAS, for example). All disks in a disk
group must be the same type (enterprise SAS, for example).
NOTE: A disk group can contain a mix of 512-byte native sector size (512n) disks and 512-byte
emulated sector size (512e) disks. For consistent and predictable performance, do not mix disks of
different sector size types (512n, 512e).
For virtual storage, a disk group of midline SAS disks will be used in the Archive tier. A disk group of
enterprise SAS disks will be used in the Standard tier. A disk group of SSDs can be used:
● In the Performance tier
● As an all-flash array
● As read cache. A virtual pool can contain only one read-cache disk group
A virtual pool cannot contain both a read-cache disk group and a Performance tier. At least one virtual
disk group must exist in a pool before a read-cache disk group can be added. A read-cache disk group
can contain a maximum of two disks.
When you add a virtual disk group, the system will first prepare the disk group to be added to a virtual
pool. During preparation, the disk group's status will be VPREP and the disk group cannot be removed.
When preparation is complete, the disk group will start initializing. During initialization, the disk group's
status will be INIT and the disk group will be available to store user data-or the disk group can be
removed.
● All virtual disk groups in the same tier in a virtual pool should have the same RAID level, capacity,
and physical number of disks. This will provide consistent performance across the tier.
● To replace a single-disk read-cache disk group with a multiple-disk read-cache disk group, simply
remove the read cache and re-add it.
NOTE:
If the only disk group in a virtual pool is quarantined, the pool will be inaccessible and
attempting to add a new disk group to that pool will fail with a "duplicate name" error. Before you
can add a disk group to that pool, you must resolve the problem with the quarantined disk group.
Minimum role manage
Syntax
add disk-group
[adapt-spare-capacity size[B|KB|MB|GB|TB|KiB|MiB|GiB|TiB]|default]
[assigned-to a|b|auto]
[chunk-size 64k|128k|256k|512k]
disks disks
[level nraid|raid0|r0|raid1|r1|raid3|r3|raid5|r5|raid6|r6|raid10|r10|
raid50|r50|adapt]
[mode online|offline]
[pool a|b]
[spare disks]
type linear|virtual|read-cache
[name]
Parameters
adapt-spare-capacity size[B|KB|MB|GB|TB|KiB|MiB|GiB|TiB]|default
Optional. For an ADAPT disk group, this specifies the target spare capacity.
● size [B|KB|MB|GB|TB|KiB|MiB|GiB|TiB] : Sets the target spare capacity to a specific
size. The unit is optional (B represents bytes). If no unit is specified, GiB will be used, regardless
of the currentbase. Whichever unit is set, internally the value will be rounded down to the nearest
GiB. If the value is set to 0, the absolute minimum spare space will be used. If this parameter is
omitted, the default setting will be used.
● default: Sets the target spare capacity to the sum of the two largest disks in the disk group,
which is sufficient to fully recover fault tolerance after loss of any two disks in the group.
assigned-to a|b|auto
Optional for linear storage. Prohibited for virtual storage. For a system operating in Active-Active
ULP mode, this specifies the controller module to own the group. To let the system automatically
Alphabetical list of commands 31