Troubleshooting for Dynamic Provisioning, Dynamic Tiering, and capacity saving

Cannot create a DP-VOL.

Causes:

• Usage of the pool has reached to 100%.
• Something in the storage system is blocked.

Solutions:

• Add some pool-VOLs to the pool. See Expanding a pool.
• Perform the operation to reclaim zero pages in order to release pages in which zero data are stored. See About releasing pages in a DP-VOL.
• Ask 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. See Pool-VOL requirements.

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 customer support to solve the problem.

A pool is blocked.

Solutions:

• Ask 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:

• Add some pool-VOLs to the pool to increase the capacity of the pool. See Expanding a pool.
• Perform the operation to reclaim zero pages in order to release pages in which zero data are stored. See About releasing pages in a DP-VOL.
• Ask 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, and that you can delete the pool.
• Ask 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:

• Check the free space of the pool and increase the capacity of the pool. See Expanding a pool.
• Perform the operation to reclaim zero pages in order to release pages in which zero data are stored. See About releasing pages in a DP-VOL.
• Ask 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:

• Check the free space of the pool and increase the capacity of the pool. See Expanding a pool.
• Perform the operation to reclaim zero pages in order to release pages in which zero data are stored. See About releasing pages in a DP-VOL.
• Ask customer support to solve the problem.

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

Causes:

• The load on the management client is too heavy, so that it cannot respond to the 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.

Causes:

• The total capacity for the DP-VOLs to be expanded exceeds the capacity for the Estimated Configurable V-VOL Capacity in the Pools window. For details, see GUID-D965DEAA-9D8C-43E2-BE72-81F9D8011291#GUID-D965DEAA-9D8C-43E2-BE72-81F9D8011291.
• To identify a cause, see GUID-B3E559C4-932C-4613-B7EF-DF6288FF0668#GUID-B3E559C4-932C-4613-B7EF-DF6288FF0668.

Solutions:

• After refreshing the display, confirm whether the processing for increasing DP-VOL capacity meets the requirements for increasing DP-VOL capacityconditions described in Requirements for increasing DP-VOL capacity.
• Retry the operation after 10 minutes or so.
• Ask customer support to solve the problem.

Cannot reclaim zero pages in a DP-VOL.

Causes:

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

Solutions:

• Make sure that the DP-VOL meets the conditions described in Releasing pages in a DP-VOL.

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:

• Make sure that the DP-VOL meets the conditions described in Releasing pages in a DP-VOL.

Cannot release the Protect attribute of the DP-VOLs.

Causes:

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

Solutions:

• Add pool-VOLs to the pool to increase the free space in the pool. See Expanding a pool.
• Perform the reclaiming zero pages operation to release pages in which zero data are stored. See Releasing pages in a DP-VOL.
• Contact 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-VOL.

SIM code 622xxx was issued.

Causes:

• Usage of the pool has reached 100%.

Solutions:

• Add pool-VOLs to the pool to increase the free space in the pool. See Expanding a pool.
• 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.

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:

• 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 that 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. See Expanding a pool.
• Perform the operation to reclaim zero pages in order to release pages in which zero data are stored. See About releasing pages in a DP-VOL.
• Confirm the display again after decreasing I/O loads of the storage system.
• Contact customer support to restore the cache memory.
• Contact 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

The shrink pool operation ends abnormally.

Causes:

• Cache memory maintenance was performed while the pool capacity was being decreased.
• Cache memory errors occurred while the pool capacity was being decreased.
• The I/O load to DP-VOLs associated with the pool is too high.
• DP-VOLs associated with the pool are being blocked.

Solution:

• Restore the cache memory, and then perform the shrink pool operation again.
• Wait until the I/O load to DP-VOLs associated with the pool is lower, and then perform the shrink pool operation again.
• Delete or format DP-VOLs associated with the pool, and then perform the shrink pool operation again.

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:

• After creating DP-VOLs, errors occur when the capacity saving setting changes to Compression or Deduplication and Compression, and then the processing aborts.

Solution:

• Resolve the causes of the errors, and then change the capacity saving setting to Compression or Deduplication and Compression by using the Edit LDEVs window.

One of the following problems occurred:

• When the capacity saving status of DP-VOLs is Enabling, the initialize processing whereby the capacity saving setting is enabled is stopped.
• When the capacity saving status of DP-VOLs is Rehydrating, the processing by which the capacity saving setting changes to disabled is stopped. Also, the progress ratio in the LDEV Properties window does not display.

Cause:

• Errors occur while the capacity saving status is changing, and then the processing aborts. After recovering from the errors, the resumed status change process fails.

Solution:

• For DP-VOLs, change Capacity Saving to Disabled, and then retry the operation by using the Edit LDEVs window.

A capacity saving status with DP-VOLs whose Deduplication Data is Disabled changes to the Failed status.

Causes:

• The shared memory is volatilized and then the storage system is started again.
• The pool is initialized.
• The pool volumes are formatted.
• The processing for deleting the DP-VOL failed.

Solution:

• Format the operation target DP-VOLs.

A capacity saving status with DP-VOLs whose Deduplication Data is Disabled changes to the Failed status.

Cause:

• The shared memory is volatilized and the storage system is restarted.
• The pool is initialized.
• The pool volumes are formatted.
• The processing for deleting the DP-VOL failed.

Solution:

• Format the operation target DP-VOLs.

A capacity saving status with DP-VOLs whose Deduplication Data is Enabled changes to the Failed status.

Causes:

• The shared memory is volatilized and the storage system is restarted.
• The pool is initialized.
• The pool volumes are formatted.
• The processing for deleting the DP-VOL failed.

Solution:

1. In the pool, back up all of the DP-VOLs whose Deduplication Data status is Enabled.
2. Block DP-VOLs in the following order: 1. DP-VOLs whose Deduplication Data status is Enabled 2. Deduplication system data volumes.
3. If you are using Storage Navigator, select the pool with which the deduplication system data volumes are associated and then launch the Initialize Duplicated Data window. If you are using CCI, specify the deduplication system data volume, and execute the raidcom initialize pool command.
4. Perform the Format LDEVs operation for the following LDEVs: Deduplication system data volumes (data store) and DP-VOLs whose Deduplication Data status is Enabled.
   CautionDo not perform the restore LDEV operation because these DP-VOLs cannot be used again.
5. Restore the back-up data, or retry the delete LDEV operation.

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:

1. For the DP-VOLs, Capacity Saving Status indicates Deleting Volume, and the progress indicates a hyphen.
2. For the DP-VOLs, Capacity Saving Status indicates Disabled.

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:

• The pool used capacity exceeded the depletion threshold.
• The target DP-VOL is being blocked.
• The pool with which the target DP-VOL is associated is being blocked, or the pool volumes are being blocked.
• The deduplication system data volume of the pool with which the target DP-VOL is associated is being blocked.
• The SVP or a Device Manager - Storage Navigator secondary window is in Modify mode.

Solutions:

If the pool used capacity exceeded the depletion threshold, take the following action:

1. Verify the free capacity of the pool, and then expand the pool capacity for the capacity shortage.

2. Perform the operation to release pages in DP-VOLs to reclaim zero pages.

If the target DP-VOL is being blocked, take the following action:

1. Restore the blocked DP-VOL.

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:

1. Restore the pool or pool volumes.

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:

• The pool used capacity exceeded the depletion threshold.
• The pool with which the target DP-VOL is associated is being blocked, or the pool volumes are being blocked.
• The deduplication system data volume of the pool with which the target DP-VOL is associated is being blocked.
• The SVP or a Device Manager - Storage Navigator secondary window is in Modify mode.

Solutions:

If the pool used capacity exceeded the depletion threshold, take the following action:

1. Verify the free capacity of the pool, and then expand the pool capacity for the capacity shortage.
2. Perform the operation to release pages in DP-VOLs to reclaim zero pages.

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:

1. Restore the pool or pool volumes.

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:

1. The cache write pending rate of CLPR for the DP-VOLs is 50% or more.
2. The controller of the storage system is being blocked.
3. The ratio of a free pool space with which the DP-VOLs are associated is 1% or less.
4. The size of a free pool space with which the DP-VOLs are associated is 120GB or less.
5. The pool with which the DP-VOLs are associated is being shrunk.
6. The pool volumes are being blocked.
7. The operation targeted DP-VOLs enabled of the capacity saving are being blocked.
8. The used capacity rate of the data store area for the operation targeted DP-VOLs enabled of the capacity saving is 80% or more.
9. The average operating ratio for MPs on basis of a controller is 70% or more.

Solutions:

• For the item number 1, reduce the written data size from hosts.
• For the item number 2, restore the blocked controller.
• For the item number 3 and 4, expand the pool capacity.
• For the item number 5, wait until the pool shrink task is completed.
• For the item number 6, restore the blocked pool volumes.
• For the item number 7, restore the blocked DP-VOLs of the operation target.
• For the item number 8, split the operation targeted DP-VOLs into DP-VOLs of that the capacity saving is enabled and whose size is 2.4TB or less.
• For the item number 9, in this case, the storage system reduces the number of processes of the initial capacity saving. If you want to increase the amount of the processing, balance the loading on a basis of a controller.

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.

• The amount of written data by hosts (the average performance of host writing) exceeds the throughput of the garbage collection (the garbage collection performance).
• The processing of the garbage collection is being stopped.

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 amount of written data by hosts exceeds the throughput of the garbage collection on a basis of a storage system, perform either of following:
  • Reduce the amount of written data by hosts.
  • Change the capacity saving setting to Disable.
  • Verify the design of pools and DP-VOLs again.

  However, if the setting of the capacity saving is changed to Disabled, the used pool capacity increases. Therefore you must verify that the pool has the enough free space before performing of the operation.

• If the amount of written data of hosts exceeds the throughput of the garbage collection on a basis of a MP unit, perform either of following:

  To rebalance the load (the writing I/Os from hosts) to MP units, change the assignment of MP units.

• If the amount of written data by hosts exceeds the throughput of the garbage collection on a basis of a DP-VOL, perform either of following:

  To rebalance the load (the writing I/Os from hosts) to DP-VOLs, divide DP-VOLDP-VOLs.

If the processing of the garbage collection is being stopped, following are possibly causes.

1. In the CLPR, the cache write pending rate is 83% or more.
2. There is no free space in the pool with which DP-VOLs are associated.
3. Pool volumes are being blocked.
4. DP-VOLs of that the capacity saving function is enabled are being blocked.

Solutions:

• For the item number 1, reduce the amount of written data by hosts, add the CLPR capacity, or change the capacity saving setting to Disable.
• However, if the setting of the capacity saving is changed to Disabled, the used pool capacity increases. Therefore you must verify that the pool has the enough free space before performing of the operation.
• For the item number 2, expand the pool capacity.
• For the item number 3, restore the blocked pool volumes.
• For the item number 4, restore the blocked DP-VOLs.

The actual performance for DP-VOLs enabled of the capacity saving is lower than the estimate.

Causes:

• The setting is not correct.
• The pool used capacity exceeds the threshold.
• The DP-VOLs are used in a task which is not suited with using of the capacity saving function.

Solutions:

1. Verify the setting. If the setting is correct, go to the step 2. If the capacity saving setting is accidentally set to Compression or Deduplication and Compression, change the setting to Disable. If the capacity saving mode is accidentally set to Inline, change the mode to Post process. For the setting of the capacity saving mode, see the command, raidcom modify ldev -capacity_saving_mode in the Command Control Interface Command Reference.
2. Verify whether the pool used capacity exceeds the warning threshold by seeing the item of Pool Usage. If the pool used capacity is not exceeded the warning threshold, go to the step 3.

   If the pool usage is exceeded the warning threshold, verify the garbage data size by seeing the item of System Data.

   If the ratio of system data size in a pool used capacity is more than 10%, the Pool Usage will go below the warning threshold by the garbage collection. The ratio of the pool used capacity goes under the warning threshold ratio, so that the I/O performance will be improved. If you know that the performance decrement is temporary and you can wait until the recovery time, waiting is the workable alternative. However, if you do not have a time to wait until the recovery, expand the pool capacity.

   If the ratio of the system data for the pool used capacity is less than 10%, expand the pool capacity.

3. If the performance of DP-VOLs is short even though there is no effect of the garbage collection, we do not recommend that you apply the capacity saving function for those volumes. Change the capacity saving function setting to Disable. However, if the setting of the capacity saving is changed to Disabled, the used pool capacity increases. Therefore you must verify that the pool has the enough free space before performing of the operation.

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:

• After deduplication system data volumes are created, errors occur while DP-VOLs are being created, and then the processing stops.

• Resolve the causes of errors. Then, repeat the task of creating DP-VOLs of which the capacity saving setting is Deduplication and Compression.

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:

• After deduplication system data volumes are created, errors occur while the settings for DP-VOLs are being changed, and then the processing stops.

• Resolve the causes of errors. Then, repeat the task of changing the capacity saving setting for DP-VOLs.

The capacity saving setting was changed to Disable. However, deduplication system data volumes are not deleted.

Cause:

• After the capacity saving setting for DP-VOLs are disabled, errors occur while deduplication system data volumes are being deleted, and then the processing stops.

• Resolve the causes of errors. Then, delete deduplication system data volumes using the CCI command, raidcom modify pool -pool -delete dsd_volumes.

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

• Remove pools that are not used.
• Remove DP-VOLs that are not used.
• Remove all unnecessary Thin Image pairs that are associated with the primary volume.
• Shrink the pool capacities.

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

• Add pool-VOLs to the pool to increase the free space in the pool.
• Reclaim zero pages to release pages in which zero data are stored.
• Contact 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 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.

• Creating pool
• Expanding pool
• Deleting 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.

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.

• If the SVP or a Device Manager - Storage Navigator secondary window is in Modify mode, change to View mode.
• The maintenance operation must be completed.
• If LDEVs cannot be created or deleted, retry the operation.
• Capacity Saving Status of DP-VOLs indicates Deleting Volume, and if the progress cannot be increased, see the troubleshooting for Dynamic Provisioning.

* xxx = hexadecimal pool number

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 raidcom extend ldev command was executed with specifying the -cylinder option to the DP-VOL for the open system.

Re-execute the raidcom extend ldev command without specifying the -cylinder option.

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.