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

2.10
Known Issues with the InForm OS
3PAR InForm OS Release Notes InForm OS Version 2.3.1 MU2
3PAR Confidential
2.7 Known Issues with the InForm OS
2.7.1 CIM Server Error Passing Maximum Length Virtual Volume Name
(Bug 55445)
The virtual volume buffer in apilib is 1 byte shorter when it should be 32 bytes including 1
byte for the null terminator. A 31 byte long virtual volume name causes
cimserver to crash.
 Workaround - Use virtual volume names of 30 bytes long or shorter to avoid this problem.
Use the setvv –name <new_name> vvname command to rename a virtual volumes over
31 bytes long.
2.7.2 Physical Copy Issue with Larger Destination Volume Size (Bug 55681)
The PblkRemain field describes how many physical blocks still remain to be copied from the
parent volume during the physical copy process. The number of blocks should always be
positive. This bug occurs when using a larger size destination volume than parent volume. The
value of
PblkRemain is calculated using the size of the parent volume rather than the size of
the destination volume.
 Workaround - Use parent and destination volumes of the same size when creating
physical copies.
2.7.3 4Gb/s 2-Port adapter Issue
The 4Gb/s 2-port Fibre Channel Adapter firmware does not detect a loss of sync when the host
reboots and has older adapters (ex: QLA2342) that do not turn off the laser.
 Workaround - None.
2.7.4 Downgrade Issues
The following are downgrade issues for InForm OS release 2.3.1 MU2.
2.7.4.1 Issues Preventing Downgrades
These issues will prevent an InServ Storage Server from downgrading from InForm OS release
2.3.1 MU2 to 2.2.4. (These issues do not apply to a downgrade from 2.3.1 MU2 to 2.3.1.)
■ Dual SD Space - Thin Provisioned virtual volumes can have two Snap Data (SD) volumes in
2.3.1 and 2.3.1 MU2. This is not a supported feature in previous InForm releases. Prior to a