Troubleshooting for Dynamic Provisioning, Dynamic Tiering, and capacity saving
Troubleshooting Dynamic Provisioning
The following table provides troubleshooting information for Dynamic Provisioning.
If you are unable to solve a problem, or if you encounter a problem not listed, please contact customer support.
When an error occurs during operations, the error code and error message are displayed in the error message dialog box. For details about error messages, see Hitachi Device Manager - Storage Navigator Messages.
Problem |
Causes and solutions |
Cannot create a DP-VOL. |
Causes:
Solutions:
|
Cannot add a pool-VOL. |
Causes:
Solution:
|
A pool-VOL is blocked. SIM code 627xxx is reported. |
Causes:
Solutions:
|
A pool is blocked. |
Solutions:
|
A pool cannot be restored. |
Causes:
Solutions:
|
A pool cannot be deleted. |
Causes:
Solutions:
|
A failure occurs to the application for monitoring the volumes installed in a host. |
Causes:
Solutions:
|
When the host computer tries to access the port, error occurs and the host cannot access the port. |
Causes:
Solutions:
|
When you are operating Hitachi Device Manager - Storage Navigator, a timeout occurs frequently. |
Causes:
Solutions:
|
DP-VOL capacity cannot be increased. |
Causes:
Solutions:
|
Cannot reclaim zero pages in a DP-VOL. |
Causes:
Solutions:
|
The DP-VOL cannot be released if the process to reclaim zero pages in the DP-VOL is interrupted. |
Causes:
Solutions:
|
Cannot release the Protect attribute of the DP-VOLs. |
Causes:
Solutions:
|
SIM code 622xxx was issued. |
Causes:
Solutions:
The Protect attribute of Data Retention Utility can have been set to DP-VOLs. After performing above solutions, release the Protect attribute of the DP-VOLs. |
SIM code 624000 was issued. |
Causes:
Solutions:
|
Formatted pool capacity displayed in the View Pool Management Status window does not increase. |
Causes:
Solutions:
|
The shrink pool operation ends abnormally. |
Causes:
Solution:
|
DP-VOLs whose capacity saving setting is Compression or Deduplication and Compression are created, but the capacity saving setting of the DP-VOLs is set to Disabled. |
Cause:
Solution:
|
One of the following problems occurred:
|
Cause:
Solution:
|
A capacity saving status with DP-VOLs whose Deduplication Data is Disabled changes to the Failed status. |
Causes:
Solution:
|
A capacity saving status with DP-VOLs whose Deduplication Data is Disabled changes to the Failed status. |
Cause:
Solution:
|
A capacity saving status with DP-VOLs whose Deduplication Data is Enabled changes to the Failed status. |
Causes:
Solution:
Note: If you format DP-VOLs for which the capacity saving setting is Disabled and Deduplication Data is Disabled, the capacity saving setting for the DP-VOLs might become Compression. If you initialize duplicated data for a pool that has DP-VOLs for which the capacity saving setting is Disabled and Deduplication Data is Enabled, the capacity saving setting for the DP-VOLs might become Deduplication and compression. Therefore, verify the capacity saving setting of DP-VOLs after the format operation completes. |
When the storage system is restarted, one of following problems occur:
|
Delete the DP-VOLs corresponding to 1 or 2 again. |
For a DP-VOL, the Capacity Saving Status indicates Rehydrating, but the processing progress does not increase. |
Causes:
Solutions: If the pool used capacity exceeded the depletion threshold, take the following action:
If the target DP-VOL is being blocked, take the following action:
If the pool with which the target DP-VOL is associated is being blocked, or if the pool volumes are being blocked, take the following action:
If the SVP or a Device Manager - Storage Navigator secondary window is in Modify mode, change to View mode. |
For a DP-VOL, the Capacity Saving Status indicates Deleting Volume, however the processing progress does not increase. |
Causes:
Solutions: If the pool used capacity exceeded the depletion threshold, take the following action:
If the pool with which the target DP-VOL is associated is being blocked, or if the pool volumes are being blocked, take the following action:
If the SVP or a Device Manager - Storage Navigator secondary window is in Modify mode, change to View mode. |
The saved capacity for the DP-VOL of which the capacity saving is enabled is not increased. |
Causes: If the saved capacity is not increased, the initial capacity saving processing might have been stopped. The initial capacity saving processing is performed on the existed data in DP-VOLs. Following are causes for the stopping of the initial capacity saving processing:
Solutions:
|
The garbage data of DP-VOLs enabled of the capacity saving is being increased. |
Causes: If the garbage data continues to increase, following are the potential of causes. However, the garbage data is included in the system data.
Solutions: Perform following if the amount of written data by hosts (the average performance of host writing) exceeds the throughput of the garbage collection (the garbage collection performance).
If the processing of the garbage collection is being stopped, following are possibly causes.
Solutions:
|
The actual performance for DP-VOLs enabled of the capacity saving is lower than the estimate. |
Causes:
Solutions:
|
The operation of creating DP-VOLs of which the capacity saving setting is Deduplication and Compression was performed. However, no DP-VOLs but deduplication system data volumes are created. |
Cause:
|
The capacity saving setting was changed from Disable to Deduplication and Compression for DP-VOLs. However, the setting of DP-VOLs is not changed and deduplication system data volumes are created. |
Cause:
|
The capacity saving setting was changed to Disable. However, deduplication system data volumes are not deleted. |
Cause:
|
SIMs for HDP/HDT
The following table lists and describes the SIM reference codes associated with Dynamic Provisioning and Dynamic Tiering operations and provides solutions for the conditions.
SIM code (SIM level) |
Event |
Thresholds or values |
Types of reports |
Solutions | |
Sent to host? |
Sent to maintenance personnel? | ||||
623xxx (Moderate) |
Error occurred in the Dynamic Provisioning pool |
Not applicable |
Yes |
Yes |
Contact customer support. |
624000 (Moderate) |
No space in the shared memory |
Not applicable |
Yes |
Yes |
Solutions
|
627xxx (Moderate) |
Pool-VOL is blocked |
Not applicable |
Yes |
Yes |
Contact customer support. |
628000 (Service) |
Protect attribute of Data Retention Utility is set |
Not applicable |
Yes |
Yes |
Solutions
After performing the above solutions, release the Protect attribute (Data Retention Utility) of the DP-VOL. |
629xxx (Moderate) |
In the Dynamic Provisioning pool, the used capacity reserved for writing exceeded the Warning Threshold. |
1% to 100% (in 1% increments) Default: 70% |
Yes |
No |
Estimate the FMD capacity to be added, and then add the FMD capacity. |
62Axxx (Moderate) |
In the Dynamic Provisioning pool, the capacity reserved for writing is full. |
100% |
Yes |
No |
Estimate the FMD capacity to be added, and then add the FMD capacity. |
62B000 (Moderate) |
In theDynamic Provisioning pool, the used capacity reserved for writing continues to exceed the highest pool threshold. SOM 734 must be enabled. |
Highest pool threshold of Dynamic Provisioning |
Yes |
No |
Estimate the FMD capacity to be added, and then add the FMD capacity. |
62Cxxx (Moderate) |
In the Dynamic Provisioning pool, the used capacity reserved for writing exceeded the Depletion Threshold. |
1% to 100% (in 1% increments) Default: 80% |
Yes |
No |
Estimate the FMD capacity to be added, and then add the FMD capacity. |
62Dxxx (Moderate) |
In the Dynamic Provisioning pool, the used capacity reserved for writing exceeded the Prefixed Depletion Threshold. |
90% |
Yes |
No |
Estimate the FMD capacity to be added, and then add the FMD capacity. |
62Exxx (Moderate) |
Dynamic Provisioning pool usage level exceeded the depletion threshold. This SIM is output when the pool option "Suspend TI pairs when depletion threshold is exceeded" is enabled. |
Depletion threshold |
Yes |
No |
Solution: Delete snapshot data and create the pair again for the Thin Image pair whose pair status is PSUE. |
631000 (Moderate) 631001 (Moderate) |
Pool-VOLs cannot be added to a pool. |
No |
Yes |
Yes |
Verify LDEV IDs that are not used.(a) If all LDEV IDs are used: Delete LDEVs that are not used.(b) In the case that the same SIM code is still reported though there are un-used LDEV IDs, or in the case that the same SIM code is still reported after performed of the solution (a), Contact customer support. |
631002 (Moderate) |
Pool-VOLs cannot be added to a pool because the maintenance work is underway for a while. |
No |
Yes |
Yes |
Verify that this SIM is not reported after performing the maintenance work. Or if this SIM is reported even though the maintenance work is not performed, Contact customer support. |
632xxx (Moderate) xxx = hexadecimal pool number |
The automatic pool volume adding processing does not perform. The pool might be in the status that the automatic pool volume adding processing cannot be performed. This SIM appears for a DP pool comprised of pool volumes assigned to accelerated compression-enabled parity groups. |
None |
Yes |
Yes |
Contact customer support. |
633xxx (Moderate) xxx = hexadecimal pool number |
The processing is suspended because a failure occurred when one of following operation is being performed on a DP pool.
LDEVs or parity groups that a pool does not contain might remain. |
None |
Yes |
Yes |
Contact customer support. |
641xxx (Service) |
In the Dynamic Tiering pool, the tier relocation operation is suspended by the system. This SIM can be displayed if "Notify an alert when tier relocation is suspended by system" is enabled on the "Edit Advanced System Settings" window. |
Not applicable |
Yes |
Yes |
Determine why the tier relocation was suspended. |
680001(Moderate) |
Failure occurred while performing the capacity saving function |
None |
Yes |
Yes | If a deduplication system data volume is associated with the pool of the selected DP-VOLs, take the following actions. (1) Back up the data of all DP-VOLs that are associated with the pool and for which Deduplication Data shows Enabled. (2) Block DP-VOLs in the following order: 1. All DP-VOLs for which Deduplication Data shows Enabled 2. All deduplication system data volumes (3) Select the pool with which deduplication system data volumes are associated,and the initialize the duplicated data. (4) Format all volumes that are associated with the pool by the following order: 1. All deduplication system data volumes (data store) 2. All DP-VOLs for which Deduplication Data shows Enabled (5) Retry the operation of changing the setting of the capacity saving. (6) Restore the backup data. If a deduplication system data volume is not associated with the pool, block and format the selected DP-VOLs, and then retry the operation. |
680002(Moderate) |
Failure occurred while deleting DP-VOLs |
None |
Yes |
Yes |
If a deduplication system data volume is associated with the pool of the selected DP-VOLs, take the following actions.(1) Back up the data of all DP-VOLs that are associated with the pool and for which Deduplication Data shows Enabled.(2) Block DP-VOLs in the following order: 1. All DP-VOLs for which Deduplication Data shows Enabled 2. All deduplication system data volumes(3) Select the pool with which deduplication system data volumes are associated,and the initialize the duplicated data.(4) Format all volumes that are associated with the pool in the following order: 1. All deduplication system data volumes (data store) 2. All DP-VOLs for which Deduplication Data shows Enabled(5) Retry the operation of changing the setting of the capacity saving.(6) Restore the backup data. If a deduplication system data volume is not associated with the pool, block and format the selected DP-VOLs, and then retry the operation. |
681xxx (Moderate) |
Deduplication system data volumes cannot be deleted. Failure occurred while deleting the deduplication system data volumes, then the processing terminated abnormally. |
None |
Yes |
No |
Take the following actions.(1) Block DP-VOLs in the following order: 1. All DP-VOLs for which Deduplication Data shows Enabled 2. All deduplication system data volumes(2) Select the pool with which deduplication system data volumes are associated,and the initialize the duplicated data.(3) Format all volumes that are associated with the pool in the following order: 1. All deduplication system data volumes (data store) 2. All DP-VOLs for which Deduplication Data shows Enabled (4) Delete deduplication system data volumes by using the CCI command, raidcom modify pool -pool -delete dsd_volumes. |
682000 (Moderate) |
Deduplication system data volumes cannot be deleted from the pool, and the deleting process is stopped. |
None |
Yes |
No |
Verify the configuration information, and then take the following actions.
|
* xxx = hexadecimal pool number |
Resolving errors when using CCI to perform Dynamic Provisioning operations (SSB1: 0x2e31/0xb96d/0xb980)
If an error occurs while using CCI to perform Dynamic Provisioning operations, you might identify the cause of the error by referring to the log appearing on the CCI window or the CCI operation log file.
The CCI operation log file is stored in the following directory.
/HORCM/log*/curlog/horcmlog_HOST/horcm.log
where
- * is the instance number.
- HOST is the host name.
The following is an example of a log entry in the CCI window.

The following table provides troubleshooting information for Dynamic Provisioning operations performed using CCI.
Error code (SSB2) |
Error contents |
Solutions |
0x0b27 |
The command cannot be executed because the virtual LDEV is not defined. |
Define the virtual LDEV and then execute the command. |
0x2c3a |
The operation was rejected because the specified volume was being enabled for the attribute of the data direct mapping. |
Specify the volume of which the attribute of the data direct mapping is disabled. |
0x2c77 |
The operation was rejected because the specified DP-VOL was a deduplication system data volume. |
Specify a DP-VOL that is not a deduplication system data volume. |
0x2c78 |
The operation failed because the specified DP-VOL is being deleted. |
Specify a DP-VOL that is not being deleted. |
0x9100 |
The command cannot be executed because user authentication is not performed. |
Perform user authentication. |
0xb900/ 0xb901/ 0xaf28 |
Error occurred when increasing DP-VOL capacity operation. |
Ask customer support to solve the problem. |
0xb902 |
The operation was rejected because the configuration was being changed by SVP or Hitachi Device Manager - Storage Navigator, or because the DP-VOL capacity was going to be increased by another instance of the CCI. |
Increase the DP-VOL capacity after finishing operations on your storage system, such as the Virtual LUN operation or a maintenance operation. See Caution in Requirements for increasing DP-VOL capacity. |
0xaf22 |
The operation was rejected because the specified volume is placed online with the OS which does not support EAV (Extended Address Volume). |
Increase the DP-VOL capacity after the specified volume is placed online with the OS which supports EAV. |
0xaf25 |
The operation to increase capacity cannot be performed on the specified DP-VOL. |
Check the emulation type of the specified DP-VOL. |
0xaf26 |
The operation was rejected because of lack of cache management devices due to increased capacity. |
Specify a capacity so that the maximum number of cache management devices will not be exceeded. |
0xaf29 |
The operation was rejected because the specified volume was not a DP-VOL. |
Makes sure that the volume is a DP-VOL. |
0xaf2a |
The operation was rejected because the specified capacities are invalid or exceeded the value immediately below LDEV Capacity in the Expand Virtual Volumes window. |
To increase capacity, specify the correct capacity that does not exceed the value immediately below LDEV Capacity in the Expand Virtual Volumes window. See the conditions for increasing DP-VOL capacity in Requirements for increasing DP-VOL capacity. |
0xaf2b |
The operation was rejected because the specified volume operation was not finished. |
Re-execute the operation after a brief interval. |
0xaf2c |
The operation was rejected because the shared memory capacity is not enough to increase the specified capacity. |
Confirm the value immediately below LDEV Capacity in the Expand Virtual Volumes window. |
0xaf2e |
The operation was rejected because the specified DP-VOL was used by other software or was being formatted. |
Wait until formatting of the specified volume is finished, or see Using Dynamic Provisioning and Dynamic Tiering with other software products and confirm whether the DP-VOL is used with software in which that the DP-VOL capacity cannot be increased. |
0xaf2f |
The specified DP-VOL capacity cannot be expanded because the configuration of journal volumes is being changed. |
Re-execute the operation after the journal volume configuration is changed. |
0x0b2b |
The operation was rejected because the
|
Re-execute the
|
0xaf60 |
The operation was rejected because the pool used capacity exceeds the depletion threshold of the pool if the specified capacity is reserved in the pool. |
Expand the pool capacity, and then retry the operation. |