Print detailed information about a specified NSS pool move. It lists the devices you are moving from and the devices you are moving to, such as
from=sdc,sdd,sde to=sdg
If a pool is cluster-enabled, the pool move is enabled and active only on the node where the pool cluster resource is currently online. On other nodes in the cluster, the pool move is not enabled.
nlvm [nlvm_options] list move <<move_name>|<pool_name>>
The move occurs as a low-level block mirror between the original location and the new location. The entire pool area is mirrored. The response reports the number of mirror regions to be moved for the pool relative to the maximum source pool size, which is unrelated to the NSS blocks in use. The region count for the old pool location does not change during the move. The complete parameter indicates the number of regions that have been moved so far and the percentage that it represents of the total number of regions to be moved.
The size of a mirror region is determined internally based on the total size of the mirror. One sector is used to track the number of mirror regions that are currently synchronized. A bit represents a mirror region, and there are 4096 bits total (512 * 8) to track. A shift technique is used so that the mirror region size is always a power of 2 (128, 256, 512, and so on) and the total number of regions to move is less than or equal to 4096. Except for very small mirrors, the number of mirror regions is usually between 2048 and 4096. The minimum mirror region size used is 64 sectors (32 KB). There is no maximum. For an 8 TB pool, the mirror region size is 2 GB. When a complete region is mirrored, the bit is set. If a region is partially mirrored during a system failure or cluster resource migration, the entire region is remirrored when mirroring resumes.
The response lists the set of devices that are being used for the original location (from) and the new location (to).
Command Option
Mandatory. Specify the name of the move, such as POOLNAME_move. You can alternatively specify the pool name.
Example
MYPOOL_move
Command Example
Print detailed information about the MYPOOL_move move.
The command returns the following information about the specified pool move:
|
Label |
Description |
|---|---|
|
Name |
Name of the move. Typically, <pool_name>_move. |
|
Pool |
Name of the pool being moved |
|
FromStat |
Status of the “from” group of devices that make up the source pool (Active, ReadError, WriteError, Missing, NotEnabled) |
|
ToStat |
Status of the “to” group of devices that make up the new instance of the pool (Active, ReadError, WriteError, Missing, NotEnabled) |
|
Complete |
Percent complete |
|
OldSize |
Size of the old/source pool in MB, GB, or TB, and the number of whole sectors in that space |
|
From |
From set of devices for the pool being moved |
|
To |
To set of devices for the pool in its new location |
|
M:M |
Major:minor numbers of the move object |
|
Regions |
Total number of mirror regions to be moved |
|
RegionsComplete |
Number of mirror regions that are complete |
Name=MYPOOL_move Pool=MYPOOL FromStat=Active ToStat=Active Complete=100% OldSize=99.00MB(202752) From=sdb To=sdc M:M=253:21 Regions=3168 RegionsComplete=3168
Name=CLUSPOOL_move Pool=CLUSPOOL FromStat=Active ToStat=Active Complete=33% OldSize=7.19GB(15087616) From=sdc,sdd,sde,sdf To=sdh M:M=253:21 Regions=3684 RegionsComplete=1245
Name=CLUSPOOL_move Pool=CLUSPOOL FromStat=NotEnabled ToStat=NotEnabled From=sdc,sdd,sde,sdf To=sdh Move is not enabled on this node.