238 Implementing the IBM Storwize V7000 with IBM Spectrum Virtualize V8.2.1
Alternatively, import and migration of external MDisks to another pool can be done by 
selecting Pools → System Migration to start system migration wizard. For more information, 
see Chapter 9, “Storage migration” on page 385. 
Include
The system can exclude an MDisk that has multiple I/O failures or has persistent connection 
errors from its storage pool. Exclusion ensures that these errors do not interfere with data 
access. If an MDisk has been automatically excluded, run the fix procedures to resolve any 
connection and I/O failure errors. 
If no error event is associated with the MDisk in the log and the external problem has been 
fixed, select Include to add the excluded MDisk back into the storage pool.
The CLI command includemdisk performs same task. It needs the MDisk name or ID to be 
provided as a parameter. See Example 6-28.
Example 6-28   Including degraded MDisk with CLI
IBM_Storwize:ITSOV7K:superuser>includemdisk mdisk3
IBM_Storwize:ITSOV7K:superuser>
Remove
In some cases, you might want to remove external MDisks from storage pools to reorganize 
your storage allocation. Select Remove to remove the MDisk from the storage pool. After the 
MDisk is removed, it goes back to unmanaged. If there are no volumes in the storage pool to 
which this MDisk is allocated, the command runs immediately without additional confirmation. 
If there are volumes in the pool, you are prompted to confirm the action, as shown in 
Figure 6-63.
Figure 6-63   Removing an MDisk from a pool
Confirming the action starts the migration of the volumes to extents from other MDisks that 
remain in the pool. When the action is completed, the MDisk is removed from the storage pool 
and returns to Unmanaged. 
Ensure that you have enough available capacity remaining in the storage pool to allocate the 
data being migrated from the removed MDisk. Otherwise, this command fails.
Important: The MDisk that you are removing must remain accessible to the system while 
all data is copied to other MDisks in the same storage pool. If the MDisk is unmapped 
before the migration finishes, all volumes in the storage pool go offline and remain in this 
state until the removed MDisk is connected again.