196 Implementing the IBM Storwize V7000 with IBM Spectrum Virtualize V8.2.1
The new pool is created and is included in the list of storage pools with zero bytes, as shown 
in Figure 6-8.
Figure 6-8   Newly created empty pool
To perform this task with the CLI, the mkmdiskgrp command is used. The only required 
parameter is extent size. It is specified with the -ext parameter, which must have one of the 
following values: 16, 32, 64, 128, 256, 512, 1024, 2048, 4096, or 8192 (MB). To create Data 
Reduction Pool, specify -datareduction yes. In Example 6-2, the command creates DRP 
named “Pool2” with no MDisks in it.
Example 6-2   mkmdiskgrp command
IBM_Storwize:ITSOV7K:superuser>mkmdiskgrp -name Pool2 -datareduction yes -ext 8192
MDisk Group, id [2], successfully created
6.1.2  Managed disks in a storage pool
A storage pool is created as an empty container, with no storage assigned to it. Storage is 
then added in the form of MDisks. An MDisk can be either an array from internal storage (as 
an array of drives) or an LU from an external storage system. The same storage pool can 
include both internal and external MDisks.
Arrays are assigned to storage pools at creation time. You cannot have an array that does not 
belong to any storage pool. They cannot be moved between storage pools. It is only possible 
to destroy an array by removing it from a pool and to re-create it with a new pool.
External MDisks can exist outside the pool. You can assign them to storage pools and remove 
them from storage pools. The MDisk object remains on a system, but its state (mode of 
operations) might change.
Naming rules: When you choose a name for a pool, the following rules apply:
/SM590000Names must begin with a letter.
/SM590000The first character cannot be numeric.
/SM590000The name can be a maximum of 63 characters.
/SM590000Valid characters are uppercase letters (A - Z), lowercase letters (a - z), digits (0 - 9), 
underscore (_), period (.), hyphen (-), and space.
/SM590000Names must not begin or end with a space.
/SM590000Object names must be unique within the object type. For example, you can have a 
volume that is named ABC and a storage pool that is calledvolumes that are 
calledvolumes called ABC.
/SM590000The default object name is valid (object prefix with an integer).
/SM590000Objects can be renamed to their current names.