Specifications

7–64 CLI Commands
The default chunk size for storagesets with less than 9 members is 256 blocks, or 128
kilobytes (K). The default chunk size for storagesets with more than 9 members is 128
blocks, or 64K. The default values provide optimal storageset performance for a wide
variety of applications. A chunk size less than 128 blocks (64K) is not recommended.
IMPORTANT: Accept the default chunk size setting for most applications. Do not
change the default setting unless you are fully aware of the impact to the
storageset’s performance.
See “Chunk Size,” page 4–43, for information regarding recommended chunk size
settings for your application.
DESTROY (Default)
NODESTROY
Controls how the metadata on the initialized container is to be handled.
NOTE: The DESTROY and NODESTROY switches are only valid with mirrorsets and
striped mirrorsets.
Specify NODESTROY to preserve forced error metadata during the initialization
process. Use the NODESTROY switch only when a unit is to be created from disk
drives REDUCED from mirrorsets. This allows the data on the container to be
accessed by a mirrorset or striped mirrorset unit. The NODESTROY switch is not
valid for RAIDsets and single-disk configurations.
Specify DESTROY to overwrite user data and forced error flags during the
initialization.
SAVE_CONFIGURATION
NOSAVE_CONFIGURATION (Default)
Instructs the controller whether to save the controller’s configuration to the container
being initialized.
The SAVE_CONFIGURATION switch requires only one disk to be initialized with
this option. However, more disks may be used, if desired, for redundancy.