HP StoreAll OS 6.5.1 Release Notes

with I/O module firmware version 7.04 and will be fixed with firmware version 7.06 or later in
a future StoreAll OS release.
• When using the FMT to update a large number of MDS600 or D6000 disk drives connected to
a 9730, the following error message displays:
Flash failed for device: Enclosure_HDD : operation timed out, but flash
for this component is still in progress.
Although this error message displays, the update is still in progress; the issue is that the timeout
value has been reached. The timeout value will be increased in a future release. To resolve this
issue, locate and verify that the *.scexe process is running. Wait until this process has completed
and then proceed with the standard reboot sequence required for the disk drives.
• On 9730 systems, the iLO can fail to power up a server when directed to do so from the iLO web
page or the iLO's Integrated Remote Console. To correct this condition, reset the iLO processor.
This can be done from the iLO web UI; select Reset on the Diagnostics page.
• When upgrading firmware of the hard disk drives (HDD) in the MDS600 and D6000 disk
enclosures, sometimes the individual HDD upgrades fail. To resolve this issue, you must downgrade
all of the drives and then retry the upgrade. This behavior is due to the underlying HDD Smart
Component used by the FMT and is under investigation.
Remote replication
• Remote replication might fail to transfer Windows Access Control Lists (ACLs) if cross-protocol
ACL synchronization is enabled on the source cluster nodes, but not on the target cluster nodes.
Before starting the replication, ensure that cross-protocol ACL synchronization is enabled on all
source and target cluster nodes.
• When remote replication is running, if the target file system is unexported, the replication of data
will stop. To ensure that replication takes place, do not unexport a file system that is the target
for a replication (for example, with ibrix_crr_export -U).
• Remote replication will fail if the target file system is unmounted. To ensure that replication takes
place, do not unmount the target file system.
• No alert is generated if the continuous remote replication target becomes unavailable. Confirm
the connection to the target system by issuing a ping command and by inspecting
ibrcfrworker.log.
• Sparse files on the source file system are replicated unsparse on the target. That is, all blocks
corresponding to the file size are allocated on the target cluster. Consequently, if the target file
system is the same size as the source file system, remote replication can fail because there is no
space left on the target file system. To work around this situation, if the source system contains
large sparse files, be sure that the target file system is larger than the source file system, and large
enough to fit all files in an unsparsed manner.
• The mountpoint /mnt/ibrix is reserved for remote replication. Hiding or blocking this mountpoint
by mounting anything over the parent /mnt will prevent Run Once replication from working at
all, and the initial domain scan of Continuous replication will fail.
• Do not add or change files or folders on the target system outside of a replication task; doing so
will make the target inconsistent with the source if a site failover occurs and some changes could
cause the task to fail. If you must access a replication target outside of a disaster recovery situation,
HP recommends that you create and access a snapshot of the target file system. This enables
read-only access to the target while removing the possibility of accidental changes being made.
• If the target file system is unmounted while an inter-cluster or intra-cluster CRR task is running, the
CRR task will not work properly. Before unmounting a file system, it is a best practice to verify
that the file system is not the target for a CRR task. If the file system is the target for a CRR task,
stop the task before unmounting the file system.
Workarounds 29