HP XP24000/XP20000 Thin Provisioning Software User Guide (T5227-96015, November 2011)

Table 15 Troubleshooting for XP Thin Provisioning (continued)
Causes and SolutionsProblems
Cause:
• Because the cache write pending rate exceeds 55 %, the
V-VOL cannot be disassociated from the pool.
Solution:
• Decrease the cache write pending rate to less than 55% by
reducing the host I/O.
A pool usage cannot be 0.
Causes:I/O errors on some writes occur on
V-VOLs
• Free space for the pool is completely exhausted. The pool
usage level is at 100%.
• Something in the storage system is blocked.
Solutions:
• Check the free space of the pool and increase the capacity
of the pool.
• Ask HP technical support to solve the problem.
Causes:When you are operating Remote Web
Console, a time-out occurs frequently.
• The load on the Remote Web Console computer is too heavy,
so the Remote Web Console computer cannot respond to the
SVP.
• The period of time until a time-out occurs is set too short.
Solutions:
• Wait for awhile, and then try the operation again.
• Verify the setting for the environment parameter of the Remote
Web Console RMI time-out period.
For information about how to set the RMI time-out period, see
the HP XP24000/XP20000 Remote Web Console User
Guide.
Causes:When the host computer tries to access
the port, an error occurs and the host
cannot access the port.
• Free space for the pool is insufficient.
• Something in the storage system is blocked.
Solutions:
• Check the free space for the pool and increase the capacity
of the pool.
• Ask HP technical support to solve the problem.
Causes:V-VOL capacity cannot be increased.
See “Troubleshooting when using XP RAID Manager” (page 79)
to identify the cause.
Solutions:
• After selecting the Refresh or Refresh All command from the
File menu at the top left of the Remote Web Console window,
make sure that the processing for increasing V-VOL capacity
meets conditions described in “Increasing V-VOL Capacity”
(page 62).
• Retry the operation in 10 minutes.
• Ask HP technical support to solve the problem.
76 Troubleshooting