Dell FluidFS Version 6.0 Release Notes

PDF

Fixed Issues in FluidFS Version 6.0.003169

This following issues were fixed in FluidFS v6.0.003169:


Area	Description
Account Management and Authentication	Dell Storage Manager listed NAS volumes for each volume folder in inconsistent or random order.
Data Protection	Scheduled replications defined from Dell Storage Manager did not adhere to Quality of Service (QoS) definitions.
	If the NDMP backup user’s password contained a single quote (‘), NDMP configuration modification hung.
	NDMP snapshot creation failed when the NAS volume name contained spaces.
	IBM Tivoli Storage Manager NDMP DMA randomly failed during a job restore operation.
Maintenance	Frequent power down activity might have prevented the cluster from starting up.
	If the Add Appliance procedure failed, the appliance could not be deleted.
	When renaming a UNIX file to the same name with different (upper/lower) case, Windows listed the file name with extra characters.
	Access to files originated in FluidFS v2 was denied, specifically if files pointed to hard links where the original entry was deleted.
	Windows sessions using continuous availability did not always fail back from node1 to node0 after a failover.
	Removing virtual IPs using Dell Storage Manager or the CLI did not affect actual system configuration.
	When choosing a directory to store diagnostics output on a NAS volume, Dell Storage Manager hung and eventually returned the following message: FluidFS Communication Failure.
NAS Volumes, Shares, and Exports	FluidFS LDAP monitoring might have impacted Active Directory systems with a large number of users, also serving LDAP (extended schema config), and degraded the performance of the FluidFS system.
	Cloned NAS volume root directory lost permissions.
	On systems bound to LDAP, If a FluidFS system was bound to LDAP and had local users defined, NFS4 file ownership might have displayed as nobody.
	Quota usage was not updated properly when ADS files were removed.
	Users could not set snapshot schedule in Dell Storage Manager if the display language was not English.
	Saving Microsoft Office files with SACL attributes resulted in the following message: There has been a network or file permission error.
	Kerberos Encryption types AES256-CTS and AES128-CTS were not supported.
	NFSv4 ACL inheritance on UNIX volume did not function properly on subfolders created from SMB clients.
	Users were unable to set/get ShareLevelPermissions attributes with PowerShell API.
	Copying using Finder and NFS4 did not work on Mac OSX, but it worked from terminal.
	NAS pool could not be expanded in system with multiple storage arrays if new size was not divisible by the number of storage arrays.
	When trying to expand a NAS pool in a system with one controller down, the following misleading message was generated: Controller0 cannot reach LUNs . NAS pool expansion was not supported in degraded mode.
	Restoring configuration of a volume failed if a share existed on both volumes, differing only by share-name case letters.
Networking	When the admin network MTU was set to 1500, the following false event was generated: NAS Controller 0 Cannot reach (using jumbo frames) host node1 on admin subnet.
	DNS suffix validation in Dell Storage Manager sometimes failed when names were valid.
	Users reported slow replication throughput over WAN.
System Management	Dell Storage Manager and CLI use opposite terminology for Lease and Oplock settings. Dell Storage Manager enables/disables the Leases and Oplocks, while the CLI enables/disables `restriction` of Leases and Oplocks.
System Management	The size-on-disk attribute for sparse files was sometimes incorrect.