Use the addmdisk command to add one
or more managed disks to an existing storage pool.
Syntax
addmdisk -mdisk { mdisk_id_list | mdisk_name_list } [ -tier { tier0_flash | tier1_flash | tier_enterprise | tier_nearline } ] { mdisk_group_id | mdisk_group_name }
Parameters
- -mdiskmdisk_id_list | mdisk_name_list
- (Required) Specifies one or more managed disk IDs or names to
add to the storage pool.
- -tiertier0_flash | tier1_flash | tier_enterprise |
tier_nearline
- (Optional) Specifies the tier of the MDisk or MDisks being added. Unless otherwise specified,
the current tier value associated with the MDisk is retained. The values are:
- tier0_flash
- Specifies a tier0_flash hard disk drive or an external MDisk for the newly
discovered or external volume.
- tier1_flash
- Specifies an tier1_flash (or flash drive) hard disk drive or an external MDisk
for the newly discovered or external volume.
- tier_enterprise
- Specifies a tier_enterprise hard disk drive or an external MDisk for the newly
discovered or external volume.
- tier_nearline
- Specifies a tier_nearline hard disk drive or an external MDisk for the newly
discovered or external volume.
The default value for a newly discovered unmanaged MDisk is enterprise.
You can change this value by using the chmdisk command.
The tier of external managed disks is not detected automatically and is set to
enterprise. If the external managed disk is made up of flash drives or nearline
Serial Attached SCSI (SAS) drives and you want to use Easy
Tier, you must either specify the tier when adding the managed disk to the storage pool or use
the chmdisk
command.
- mdisk_group_id | mdisk_group_name
- (Required) Specifies the ID or name of the storage pool to add
the disks to. When an MDisk is added, the warning threshold for
the storage pool is automatically scaled.
Description
This
command adds the managed disks that you specify to the storage pool.
Remember: This command cannot be used for child
pools.
The disks can be specified in terms of the managed
disk ID or the managed disk name. The managed disks must be in unmanaged
mode.
Disks that already belong to a storage pool cannot be
added to another storage pool until they have been deleted from their
current storage pool. You can delete a managed disk from a storage
pool under the following circumstances:
- If the managed disk does not contain any extents in use by a volume
- If you can first migrate the extents in use onto other free extents
within the storage pool.
Remember: Do not
include an Mdisk in an storage pool if it can only be used in image
mode.
If the system has I/O groups that are not capable of
encryption, you cannot add the MDisk if the MDisk group has an encryption
key and the MDisk is not self-encrypting.
An invocation example
addmdisk -mdisk mdisk13:mdisk14 -tier tier_nearline Group0
The resulting output:
No feedback