Example 6-10 chmdiskgrp to rename child pool IBM_Storwize:ITSOV7K:superuser>chmdiskgrp -name Pool0_child_new -size 45056  Pool0_child0 IBM_Storwize:ITSOV7K:superuser> Deleting a child pool is a task similar to deleting a parent pool. As with a parent pool, the  Delete  action is disabled if the child pool contains volumes, as shown in Figure 6-22.  Figure 6-22 Deleting a child pool After you delete a child pool, the extents that it occupied return to the parent pool as free  capacity. To delete a child pool with the CLI, use  rmmdiskgrp . To move a volume to another pool, you can use migration or volume mirroring in the same  way you use them for parent pools. For more information about volume migration and volume  mirroring, see Chapter 7, “Volumes” on page 241. The system supports migration of volumes between child pools within the same parent pool  or migration of a volume between a child pool and its parent pool. Migrations between a  source and target child pool with different parent pools are not supported. However, you can  migrate the volume from the source child pool to its parent pool. The volume can then be  migrated from the parent pool to the parent pool of the target child pool. Finally, the volume  can be migrated from the target parent pool to the target child pool.  During a volume migration within a parent pool (between a child and its parent or between  children with same parent), there is no data movement but only extent reassignments. Volume migration between a child storage pool and its parent storage pool can be performed  in the  Volumes  menu, on the  Volumes by Pool  page. Right-click a volume and choose to  migrate it into a suitable pool.  In the example on Figure 6-23 on page 207, volume  child_volume  has been created in child  pool  Pool0_child0.  Notice that child pools appear exactly like parent pools in the Volumes by  Pool pane. Migrating volumes to and from child pools 206  Implementing the IBM Storwize V7000 with IBM Spectrum Virtualize V8.2.1