3PAR InForm OS 2.3.1 MU2 Release Note (325-200142 Rev B, October 2010)

2.16
Known Issues with the InForm OS
3PAR InForm OS Release Notes InForm OS Version 2.3.1 MU2
3PAR Confidential
2.7.13 Remote Copy Volumes go Stale Due to Lack of Adm Space (Bug 44963)
The default grow value of 64 GB might be insufficient for volumes which are in Remote Copy
groups. The reason is Remote Copy relies on taking snapshots during the initial sync phase and
also during the resync periods. The snapshots end up using administrator space depending on
the IOPS and throughput load on the Remote Copy volumes.
 Workaround - Use setcpg -sdgs <increment_value> <volume_name> to increase the
default grow increment. The recommended value is 96 GB.
2.7.14 controlport Configuration Gives Warning after Being Taken Offline
(Bug 44989)
Using the -f option with controlport config, the system responded with a confirmation
request, or refused to force the mode change.
 Workaround - If the -f flag was used and the system still prompts for confirmation,
respond to the prompt. If there are other messages, they need to be resolved (e.g. take
port offline), or possibly reissue the command.
2.7.15 createvvcopy Issues with Halt (Bug 45142)
When a virtual volume copy is halted, the detailed status of the target virtual volume indicates
copy_failed. The detailed status of the target virtual volume continues to show this state even
if the virtual volume copy is restarted and the virtual volume copy is going on.
 Workaround - The virtual volume detailed status is cleared once the restarted virtual
volume copy completes. No user intervention is required.
2.7.16 Disk Failure Alert has Invalid/Incorrect Magazine Information
(Bug 45224)
A disk drive failure alert may not correctly identify its corresponding drive magazine location.
When a disk is considered "missing" by the system, the alert will identify the Drive Magazine
as "N/A" (Not Available). For example, "Message : Magazine N/A, Physical Disk 104 Failed."
 Workaround - The Physical Disk drive number is correctly displayed in the alert and in the
InServ Storage Server's event log. Examine the CLI output of the showpd and showpd -s
commands to determine the cage/magazine location of the failed disk.