HP StorageWorks XP Remote Web Console Software - Manual (Page 81)

Table 15 Troubleshooting for XP Thin Provisioning (continued)
Causes and Solutions Problems
Cause:
• After the pool is disassociated from any V-VOL, the pool usage
is not 0.
•
External volumes were not removed from the pool.
Solutions:
•
Confirm that the pool usage is 0, and then delete the pool.
•
Ask HP Technical Support to solve the problem.
A pool cannot be deleted.
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:
• 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.
I/O errors on some writes occur on
V-VOLs
Causes:
•
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 StorageWorks XP24000/XP20000 Remote Web
Console User Guide.
When you are operating Remote Web
Console, a time-out occurs frequently.
Causes:
•
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.
When the host computer tries to access
the port, an error occurs and the host
cannot access the port.
XP Thin Provisioning Troubleshooting 81