HP XP P9500 Storage User Manual
Page 165
Causes and Solutions
Problems
Causes:
Cannot create a THP V-VOL.
•
Usage of the pool has reached to 100%.
•
Something in the storage system is blocked.
•
Too many THP V-VOLs are assigned, or Subscription Limit is too low.
Solutions:
•
Add some pool-VOLs to the pool. See
.
•
Increase the value of Subscription Limit for the pool. See
the pool subscription limit ” (page 107)
.
•
Ask the HP Technical Support to solve the problem.
Causes:
Cannot add a pool-VOL.
•
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” (page 64)
Causes:
•
A failure occurred in two or more data drives.
Solutions:
•
Ask the HP Technical Support to solve the problem.
A pool-VOL is blocked. SIM code 627XXX is
reported.
Causes:
•
The breaker has been turned off and the shared memory has been
lost, and then the system has been started.
Solutions:
•
Ask the HP Technical Support to solve the problem.
A pool is blocked.
Causes:
A pool cannot be restored.
•
Processing takes time, because something in the storage system is
blocked.
•
The pool-VOL is blocked.
•
The THP V-VOL capacity has increased but has been reduced back
to the previous THP V-VOL capacity.
•
Usage of the pool has reached to 100%.
Solutions:
•
After waiting for a while, click Refresh or Refresh All from the File
menu at the top left of the Remote Web Console window, and then
check the pool status.
•
If you increased the THP V-VOL capacity but the THP V-VOL capacity
has been reduced back to the previous THP V-VOL capacity, follow
the instructions in
“Requirements for increasing THP V-VOL capacity”
to make sure that the capacity is increased, and then
restore the pool.
•
Add some pool-VOLs to the pool to increase the capacity of the pool.
See
“Increasing pool capacity” (page 111)
).
•
Ask the HP Technical Support to solve the problem.
Troubleshooting Thin Provisioning
165