Chapter 7. Volumes 309
You can run the lsmigrate command at any time to see the status of the migration process, 
as shown in Example 7-30.
Example 7-30   The lsmigrate command
IBM_2145:ITSO_CLUSTER:superuser>lsmigrate
migrate_type MDisk_Group_Migration
progress 0
migrate_source_vdisk_index 27
migrate_target_mdisk_grp 2
max_thread_count 4
migrate_source_vdisk_copy_id 0
IBM_2145:ITSO_CLUSTER:superuser>lsmigrate
migrate_type MDisk_Group_Migration
progress 76
migrate_source_vdisk_index 27
migrate_target_mdisk_grp 2
max_thread_count 4
migrate_source_vdisk_copy_id 0
7.8.17  Migrating a fully managed volume to an image mode volume
Migrating a fully managed volume to an image mode volume enables the IBM Spectrum 
Virtualize system to be removed from the data path. This feature might be useful when the 
IBM Spectrum Virtualize system is used as a data mover.
To migrate a fully managed volume to an image mode volume, the following rules apply:
/SM590000Cloud snapshots must not be enabled on the source volume.
/SM590000The destination MDisk must be greater than or equal to the size of the volume.
/SM590000The MDisk that is specified as the target must be in an unmanaged state.
/SM590000Regardless of the mode in which the volume starts, it is reported as a managed mode 
during the migration.
/SM590000If the migration is interrupted by a system recovery or cache problem, the migration 
resumes after the recovery completes.
Note: If insufficient extents are available within your target storage pool, you receive an 
error message. Ensure that the source MDisk group and target MDisk group have the 
same extent size.
You can use the optional threads parameter to control priority of the migration process. The 
default is 4, which is the highest priority setting. However, if you want the process to take a 
lower priority over other types of I/O, you can specify 3, 2, or 1.
Progress: The progress is shown in terms of percentage complete. If no output is 
displayed when running the command, all volume migrations finished.