Release Notes

Release Notes— Fluid Cache for SAN for Linux Systems
Known Issues Arising from Third Party Software
The following issues are not caused by Fluid Cache itself, but arise from known issues in third
party software.
Low Memory Handling Issues
ISSUE: When the system is low on memory, memory allocation errors, I/O timeouts, and
EAGAIN errors (resource temporarily unavailable) may appear.
WORKAROUND: Add or free up RAM memory.
OpenManage Installation Causes RDMA to Fail
ISSUE: On SLES 11 SP3, if you install the Mellanox drivers and afterward install OpenManage
7.4, the installation of libmlx4-rdmav2 breaks the already installed RDMA configuration and
Fluid Cache runs in TCP mode instead of RDMA.
WORKAROUND: Reinstall the Mellanox drivers after installing OpenManage and before
installing Fluid Cache.
JDK Installer Generates Log Messages
ISSUE: Installing Fluid Cache after installing jdk-7u6-linux-x64.rpm causes the JDK installer to
send harmless messages to log. This is a known Oracle and Java bug that occurs only on SLES.
WORKAROUND: Add a Required-Stop section to the jexec init script to stop the messages from
being generated. In the file /etc/init.d/jexec, enter the following line:
# Required_Stop:
Volume Manager Disk Creation
ISSUE: Attempts to use Volume Manager to create a volume on a Fluid Cache disk fail with the
following error: Device /dev/fldc0 not found (or ignored by filtering)
WORKAROUND: Volume Manager is not supported by Fluid Cache, and should not be used to
create volumes out of Fluid Cache disks. Instead, create a volume on the backend store and
then cache that volume.
Dell - Internal Use - Confidential
Confidential Page 7 5/5/2015