HP XP7 Storage User Manual
Page 139
Causes and solutions
Problem
Causes:
You cannot create FS pairs.
•
You have reached the maximum amount of cache management devices.
•
You have not met the prerequisites to create the pair.
•
The status of the specified volume is not displayed because you are deleting the FS pair.
Solutions:
•
Make sure that you have enough cache management devices to create the pairs (see
Snap cache management device requirements” (page 33)
).
•
If cache management devices are running out, complete one of the following:
◦
Delete unnecessary external volumes.
◦
Delete unnecessary V-VOLs.
◦
Delete the FS pairs related to the P-VOL.
•
Complete the following:
1. Fulfill the conditions to create the pair
2. Create the pair.
Cause: The consistency group contains an FS pair whose status cannot be changed.
A timeout occurs and the RAID
Manager command ends
Solution: Resolve the error condition and perform pair tasks (see
“Issues and abnormal termination
when splitting pairs” (page 155)
and
“Workflow for troubleshooting storing snapshot data for
).
abnormally (error code
EX_EWSTOT).
Causes:
FS pairs are not displayed in
the volume list.
•
You have not created the FS pairs.
•
The filtering function is prohibiting the displaying of the pairs.
Solutions:
•
Create the FS pairs.
•
Change the settings in the Display Filter dialog box.
Cause: A volume is blocked because a failure occurred in the data drive.
An error occurred while
restoring the pair.
Solution:
1.
Delete the blocked FS pair (see
“Deleting Fast Snap pairs” (page 85)
).
2.
contact HP Technical Support.
Causes:
A volume is blocked.
•
A failure occurred in at least two data drives.
•
The breaker was turned off once and then the power supply switched on.
Solution: contact HP Technical Support.
Cause: Access to the volume is rejected.
A problem occurred in the host
application for monitoring the
volumes.
Solution:
1.
Stop the host application monitoring the volumes.
2.
Split all of the pairs (“PSUS” status) (see
“Splitting Fast Snap pairs to store snapshot data”
).
3.
Start the monitoring application on the host and check whether the host has access to pair
volumes (see
“Fast Snap pair status” (page 15)
).
Cause: Access to the volume is rejected.
A virtual volume cannot be
recognized correctly after the
Solution:
host server is booted/rebooted
1.
Stop the host application monitoring the volumes.
or the command for
recognizing a device is
performed.
2.
Split all of the pairs (“PSUS” status) (see
“Splitting Fast Snap pairs to store snapshot data”
).
General troubleshooting
139