Release Notes

Release Notes— Fluid Cache for SAN for VMware Systems
unable to map cached volumes since doing a couple of VSA failures
Extra claimrules attached to a LUN in the journal.
claim rule files and path files in /tmp on the VSA are not being cleaned up
incomplete error handling in add_claim.sh when esx operations fail
lost all paths to devices on primary cfm fail/recover
cache server takes a very long time to reconnect to cluster after vsa failure
CS complaining about being unable to open a backing store device even though it is up
accessible and available on all nodes
Client should handle TUR directly, don't pass them through to device
the timer for starting the set_preferred_path work isn't long enough and shouldn't be run
while mapping
rnablk_generic_cmd accesses ios after com_send, can race with completion
MD asserted due a cache device mis-match in cache response
Block location check in node failure test - MD may have incorrectly declared an entry
vestigial and deleted it
Block stuck in INVD_SENT in cache device fail test, ios timeouts result
Activation and connection status for not-activated CS should be displayed
ios timeouts due to stuck replica writes
ESXi 6.0 - "Set logical unit policy" vsphere tasks don't run after mapping LUNs
network failure test hit CS segfault in ping_ctx_register
CFM segfault in free_lun_info
Agent didn't restart CS when requested to do so
Dell - Internal Use - Confidential
Page 5 3/9/2015