rmmdisk

Use the rmmdisk command to delete a managed disk (MDisk) from a storage pool.

Syntax

rmmdisk -mdisk { mdisk_id_list | mdisk_name_list } [ -force ] { mdisk_group_id | mdisk_group_name }

Parameters

-mdiskmdisk_id_list | mdisk_name_list: (Required) Specifies one or more managed disk IDs or names to delete from the group.
-force: (Optional) Migrates data on the specified disks to other disks in the group. The command completes asynchronously if -force is specified.
mdisk_group_id | mdisk_group_name: (Required) Specifies the ID or name of the storage pool to delete the disks from. The warning threshold for a storage pool is automatically scaled when MDisks are deleted.
Note: The command cannot be used with image-mode volumes.

Description

This command attempts to remove the managed disk or disks from the group.

Remember: This command cannot be used for child pools.

Deleting a managed disk from a group can only be done if the managed disk does not contain any extents in use by a volume. If there are extents in use and you do not supply the force flag, the command fails.

Attention: If this disk being removed has already been powered down, removed, or is experiencing a power outage, the migration is pending and does not complete until the MDisk comes back online. The MDisk is not removed from the list of MDisks that are contained in the group.

If the disk has been deliberately removed, the only method of removing the MDisk is to remove the entire group itself.

Ensure that you do not destroy any controller LUNs until you have deleted them from the storage pool that they belong to.

The rmmdisk command fails if there are insufficient free extents on other disks in the storage pool for the duration of the command.

If you do specify the force flag, an attempt will be made to migrate the extents that are in use onto other free extents within the storage pool. If there are not enough free extents in the storage pool, the command will fail even if the force flag is specified.

When an array MDisk is in a storage pool, five extents in the storage pool are reserved for internal use. If you attempt to remove an MDisk when an array MDisk is in the storage pool, the command will fail (even if the -force flag is specified), if five free extents do not remain in the storage pool.

To delete the disks from the group, you have the following options:

You can delete the volume that is using the extents specified on the managed disk.
You can add more managed disks to the group, rerun the command and specify the -force parameter.

When data is being migrated from the managed disk, it might take some time for the command to complete. The command itself will return with a success code, notifying you that migration is in progress (if migration is required). An event is logged when the migration is complete and the disk is deleted from the group at this time. You can also check the progress of any active migrations by running the lsmigrate command.

If you specify -force, the rmmdisk command fails if there are offline MDisks. If there are no online quorum disks the migration fails.

Remember: When using the -mdisk parameter, MDisks are removed if there is one (or more) SAS MDisk specified in the list.

An invocation example

rmmdisk -mdisk mdisk12 -force Group3

The resulting output:

No feedback