Release Notes

18 Known Issues
Issue ID Functional
Area
Description Workaround/Resolution
MDT-137232 Storage - File
Under rare circumstances, NAS services
could be disrupted, if the appliance is
close to reaching the maximum used data
capacity.
Take one of the following actions on the
appliance on which the NAS service is
installed: add capacity to the appliance (for
example, add drives or expansion
enclosures), increase free capacity on the
system (for example, deleting unused
snapshots, volumes) , or migrate data off
the system.
MDT-210085 Storage - File
Unable to add a Tree Quota to a File
system because there the description is
too large (more than 512 bytes).
Add a shorter description to the Tree Quota.
MDT-195652 Storage - File
Unable to remove the description from an
NFS Export.
To change the description, overwrite the
current description with a blank character
space. Save the NFS Export with no
description, then go back and update the
description again.
MDT-148608 SupportAssist
Attempts to upload Support Materials fail.
SupportAssist is unable to upload files
when there is insufficient free space in the
system partition.
Delete old Data Collections to increase the
available space in the file system so that
SupportAssist can make a backup copy of
the file for upload.
MDT-153771 SupportAssist
Enabling either Direct connect with
remote access or Gateway connect with
remote access may fail.
If enabling either higher tier type, Direct
connect with remote access or Gateway
connect with remote access, fails, wait for
the backend issue to clear, then do the
following:
1. Enable the related lower tier type, Direct
connect without remote access or Gateway
connect without remote access.
2. Disable the related lower tier type.
3. Re-enable the higher tier type, Direct
connect with remote access or Gateway
connect with remote access type.
If the issue persists, contact your service
provider.
MDT-109970 Virtualization
Unable to create a vVol storage container
in PowerStore, after having just deleted a
vVol datastore with the same name from
vSphere.
Either create the vVol storage container in
PowerStore using a different name or allow
some more time before creating the new
vVol storage container in PowerStore with
the same name that was used in vSphere.