Troubleshooting Dynamic Provisioning

The following table provides troubleshooting instructions for Dynamic Provisioning.

Problems

Causes and Solutions

Cannot create a DP-VOL.

Causes:

  • Usage of the pool has reached to 100%.

  • Something in the storage system is blocked.

  • The available capacity of DP-VOL is restricted due to the value of Subscription-Limit set for the pool.

Solutions:

  • Perform the operation to reclaim zero pages in order to release pages in which zero data are stored. See Releasing pages in a DP-VOL.

  • Ask the customer support to solve the problem.

Cannot add a pool-VOL.

Causes:

  • 1,024 pool-VOLs are already defined in the pool.

  • The pool-VOL does not fill the requirements for a pool-VOL.

  • Something in the storage system is blocked.

Solution:

  • Change the setting of the LDEV to satisfy the requirement of the Pool-VOL. .

A pool-VOL is blocked. SIM code 627xxx is reported.

Causes:

  • A failure occurred in data drives greater than the parity group redundancy. The redundancy of the parity group depends on the number of the blocked PDEVs (data drives). For example:

  • When the parity group configuration is 3D+1P and failures occur in two or more drives, the failures are considered to have occurred in data drives beyond the parity group redundancy.

  • When the parity group configuration is 6D+2P and failures occur in three or more drives, the failures are considered to have occurred in data drives beyond the parity group redundancy.

Solutions:

  • Ask the customer support to solve the problem.

A pool is blocked.

Solutions:

  • Ask the customer support to solve the problem.

A pool cannot be restored.

Causes:

  • Processing takes time, because something in the storage system is blocked.

  • Usage of the pool has reached to 100%.

Solutions:

  • Perform the operation to reclaim zero pages in order to release pages in which zero data are stored. See Releasing pages in a DP-VOL.

  • Ask the customer support to solve the problem.

A pool cannot be deleted.

Causes:

  • The pool usage is not 0.

  • External volumes are removed from the pool before you delete the pool.

  • DP-VOLs have not been deleted.

Solutions:

  • Confirm that the pool usage is 0 after the DP-VOLs are deleted, then you can delete the pool.

  • Ask the customer support to solve the problem.

A failure occurs to the application for monitoring the volumes installed in a host.

Causes:

  • Free space of the pool is insufficient.

  • Some areas in the storage system are blocked.

Solutions:

  • Perform the operation to reclaim zero pages in order to release pages in which zero data are stored. See Releasing pages in a DP-VOL.

  • Ask the customer support to solve the problem.

When the host computer tries to access the port, error occurs and the host cannot access the port.

Causes:

  • Free space of the pool is insufficient.

  • Some areas in the storage system are blocked.

Solutions:

  • Perform the operation to reclaim zero pages in order to release pages in which zero data are stored. See Releasing pages in a DP-VOL.

  • Ask the customer support to solve the problem.

When you are operating Device Manager - Storage Navigator, a timeout occurs frequently.

Causes:

  • The load on the management client is too heavy, so that it cannot respond to SVP.

  • The period of time until when time-out occurs is set too short.

Solutions:

  • Wait for a while, then try the operation again.

DP-VOL capacity cannot be increased.

See Troubleshooting provisioning while using Command Control Interface and identify the cause.

Solutions:

  • Retry the operation after 10 minutes or so.

  • Ask the customer support to solve the problem.

Cannot reclaim zero pages in a DP-VOL.

Causes:

  • Zero pages in the DP-VOL cannot be reclaimed because the DP-VOL does not meet conditions for releasing pages in a DP-VOL.

Solutions:

The DP-VOL cannot be released if the process to reclaim zero pages in the DP-VOL is interrupted.

Causes:

  • Pages of the DP-VOL are not released because the process of reclaiming zero pages was interrupted.

Solutions:

Cannot release the Protect attribute of the DP-VOLs.

SIM code 628000 was issued.

Causes:

  • The pool is full.

  • The pool-VOL is blocked.

  • The pool-VOL that is an external volume is blocked.

Solutions:

  • Contact the customer support to restore the pool-VOL.

  • If the blocked pool-VOL is an external volume, verify the status of the path blockade and the external storage system.

  • After performing above solutions, release the Protect attribute (Data Retention Utility) of the DP-VOLs. For information about Data Retention Utility, see relevant chapters in this user guide.

SIM code 624000 was issued.

Causes:

  • The pools and DP-VOLs configuration, of which the size is more than the supported capacity, is created.

Solutions:

  • Remove pools that are not used.

  • Remove DP-VOLs that are not used.

  • Remove Thin Image pairs that are not used.

  • Shrink pools capacities.

Formatted pool capacity displayed in the View Pool Management Status window does not increase.

Causes:

  • Another pool is being formatted.

  • The pool usage level reaches up to the threshold.

  • The pool is blocked.

  • I/O loads to the storage system are high.

  • The cache memory is blocked.

  • Pool-VOLs are blocked.

  • Pool-VOLs which are external volumes are blocked.

Solutions:

  • Confirm the display again after waiting for a while.

  • Add pool-VOLs to the pool to increase the free space in the pool. For more information, see Increasing pool capacity .

  • Perform the operation to reclaim zero pages in order to release pages in which zero data are stored. See Releasing pages in a DP-VOL.

  • Confirm the display again after decreasing I/O loads of the storage system.

  • Contact the customer support to restore the cache memory.

  • Contact the customer support to restore the pool-VOL.

  • If the blocked pool-VOL is an external volume, confirm following:

  • Path blockage

  • Status of the storage system

If you are unable to solve a problem using the above suggestions, or if you encounter a problem not listed, please contact the customer support.

If an error occurs during the operations, the error code and error message appear in the error message dialog box. For more information about error messages, see Device Manager - Storage Navigator Messages.