• Powering down the NAS cluster solutioncontrollersThe file system may take a long time to clean the cache tothe storage either due to lot of data, or due to anintermittent connection to the storage.During the powering down stage, the issue could be dueto the OS kernel hanging on the controller or failing tosync its state to the local drive.Workaround If the file system has stopped and if one of the controllersare still up, you can physically power down the controllerusing the power button.If file system has not stopped, you must let it continueworking. The file system reaches a 10 minute timeout,flushes its cache to the local controllers, and continuesthe shutdown process.NAS Container Security ViolationDescription NAS container security violation.Cause Selecting security style for a NAS container dictates thedominant protocol to be used to set permissions on files inthis volume. NFS for UNIX security style volumes and CIFSfor NTFS security style volumes.Consequently, this makes some operations invalid:• Setting UNIX permissions for a file in an NTFSSecurity style container.• Setting UID/GID ownership for a file in an NTFSSecurity style container.• Setting ACL for a file in a UNIX Security stylecontainer.• Changing read-only flag for a file in a UNIXSecurity style container.• Setting SID/GSID ownership for a file on UNIXSecurity style container.The NAS container security style must reflect the mainprotocol used to access its files.Workaround If a user frequently needs to perform a cross-protocolsecurity related activity, split the data into separate NAScontainers based on the main access protocol.Multiple Errors Received During File System FormatDescription You receive multiple errors during a file system format.Cause Probable causes may be:• Wrong SAN IPs are used in the Dell NAS InitialDeployment Utility (IDU).• Wrong IQNs used while defining hosts in theMDSM.94