Dell PowerStore 5200T EMC PowerStore Release Notes for PowerStore OS Version 3 - Page 17

Issue ID MDT-388534 MDT-384468 MDT-383323 MDT-383296 MDT-381213 MDT-374198 MDT-351596 MDT-337758 MDT-256564 MDT-216934 MDT-60851 MDT-261900 MDT-252443 Functional Area Description Storage - Block Storage - Block Storage - Block Storage - Block Storage - Block Storage - Block Storage - Block Storage - Block Storage - Block Storage - Block Storage - File Storage - File Storage - File LUN IDs 254 and 255 are reserved from use by VMware ESXi. If performing volume creations in quantiles greater than one and are utilizing automatic LUN ID assignment, these LUN IDs could be utilized resulting in the volume creation failing for those specific volumes. Rolling DP panics caused by a race condition while writing 1MB UNMAP record to the log. The race condition occurs between the page lookup in the TxCache and adding its LoggingOffset to the dirty/free list. Internal appliance communication may result in excessive communication sessions. This can cause memory strain to services and impact web UI function, Data Collection creation, excessive local boot drive capacity usage, etc. An internal configuration allowed Host-LUN Unit numbers greater than 254 to be presented to Windows Hosts, which Windows does not support. The array no longer automatically assigns HLUs higher than 254 to Windows hosts when mapped In rare cases snapshot creation can hit a timeout, the mechanism in this release has been improved to avoid similar failures. Internal System Manager Stuck due to removing a not-exiting drive caused by a software race condition. During metadata processing a race condition could cause storage services to restart on a node. Metadata corruption may be reported due to issue with the hardware response for compression In multi-appliance cluster standby replica management database may not start on nonprimary appliance due to corruption, leading to nodes rebooting and entering service mode. In rare cases a faulted drive can lead to node inability to see drives. This is due to firmware for internal PCIe switch used for drive connectivity locking up. NAS server start and stop actions may generate notification events with the NAS server name incorrectly displayed as "RECOVERDMn" in the description. Where the "n," in "RECOVERDMn," is the numeric address of the NAS server. Modification of NFS exports host IP's from PowerStore Manager defaults to include 255.255.255.255 subnet which is considered an invalid netmask and therefore not accepted. An error occurred when setting a user quota on an SMB share when the user name was created with the SID (security identifier). MDT-239733 Storage - File MDT-222985 Storage - File MDT-214093 Storage - File MDT-210085 Storage - File MDT-201821 Storage - File Unable to enable "Notify on Write Enabled," and "Notify on Access Enabled," options on a clone of a multiprotocol File System. When creating, or removing an NFS server, from a NAS Server that has been named with over 15 characters, the request to add or remove the NFS Server from the NAS server times out. An erroneous error is returned, "Not LDAP for NAS Server ," when assigning an LDAP Server IP address that is not RFC-2307 compliant, in the User Quota assigned to the NAS Server. Unable to add a Tree Quota to a File system because there the description is too large (more than 512 bytes). The Kerberos port number was changed using the PowerStore REST API Patch command. However, after sending the GET request from the PowerStore REST API, the port was not updated with the new port number. Resolved Issues 17