Product Release Notes

Product Release Notes
Revision A0
June 2014
Important Information
Information in this document is subject to change without notice and does not represent a commitment on
the part of DataDirect Networks, Inc. No part of this manual may be reproduced or transmitted in any
form or by any means, electronic or mechanical, including photocopying and recording, for any purpose
other than the purchaser’s personal use without the written permission of DataDirect Networks, Inc.
© 2014 DataDirect Networks, Inc. All rights reserved.
DataDirect Networks, the DataDirect Networks logo, DirectOS, DirectProtect, DirectMon, EXAScaler,
GRIDScaler, Information in Motion, NAS Scaler, NoFS, ObjectAssure, SATAssure, Silicon Storage
Appliance, S2A, Storage Fusion Architecture, SFA, Storage Fusion Fabric, Storage Fusion Xcelerator, SFX,
xSTREAMScaler, Web Object Scaler, WOS are registered trademarks or trademarks of DataDirect
Networks, Inc. All other brand and product names are trademarks of their respective holders.
DataDirect Networks makes no warranties, express or implied, including without limitation the implied
warranties of merchantability and fitness for a particular purpose of any products or software. DataDirect
Networks does not warrant, guarantee or make any representations regarding the use or the results of the
use of any products or software in terms of correctness, accuracy, reliability, or otherwise. The entire risk
as to the results and performance of the product and software are assumed by you. The exclusion of
implied warranties is not permitted by some jurisdictions; this exclusion may not apply to you.
In no event will DataDirect Networks, their directors, officers, employees, or agents (collectively
DataDirect Networks) be liable to you for any consequential, incidental, or indirect damages, including
damages for loss of business profits, business interruption, loss of business information, and the like,
arising out of the use or inability to use any DataDirect product or software even if DataDirect Networks
has been advised of the possibility of such damages by you. Because some jurisdictions do not allow the
exclusion or limitation of liability for consequential or incidental damages, these limitations may not apply
to you. DataDirect Networks liability to you for actual damages from any cause whatsoever, and
regardless of the form of the action (whether in contract, tort including negligence, product liability or
otherwise), is limited to the sum you paid for the DataDirect product or software.
DataDirect Networks
WOS™ Access 1.2.5 Release Notes Revision A0 | 2
TABLE OF CONTENTS
1.0 OVERVIEW ..................................................................................................................................................... 4
2.0 SUPPORTED CONFIGURATIONS ................................................................................................................. 4
2.1
Hardware .......................................................................................................................................................................... 4
2.2
Protocols ........................................................................................................................................................................... 4
2.3
Client Operating Systems........................................................................................................................................... 4
2.4
WOS .................................................................................................................................................................................... 4
2.5
Technology Preview ..................................................................................................................................................... 4
2.6
Not Supported ................................................................................................................................................................ 4
3.0 INSTALLATION .............................................................................................................................................. 5
3.1
Pre-requisite .................................................................................................................................................................... 5
3.2
Upgrade ............................................................................................................................................................................ 5
4.0 CHANGES SINCE LAST RELEASE .................................................................................................................. 5
5.0 KNOWN ISSUES ............................................................................................................................................. 6
5.1
Active Directory ............................................................................................................................................................. 6
5.2
CIFS ..................................................................................................................................................................................... 6
5.3
NFS ...................................................................................................................................................................................... 7
5.4
Namespace Synchronization .................................................................................................................................... 7
5.5
Services Relocation ....................................................................................................................................................... 8
5.6
TrashCan Feature........................................................................................................................................................... 8
6.0 SUPPORT ....................................................................................................................................................... 9
DataDirect Networks
WOS™ Access 1.2.5 Release Notes Revision A0 | 3
1.0
Overview
This document applies to the WOS Access version 1.2.5 release. It details upgrade
procedures, supported configurations, resolved issues, and known issues with
workarounds wherever applicable.
2.0
Supported Configurations
WOS Access 1.2.5 supports the following hardware, protocols, and client operating
systems.
2.1
Hardware
WOS Access 1.2.5 supports the following hardware configurations:
2.2
•
DDN WOS Access Gateway Servers with 4x300TB (1.2TB total, 600GB usable)
SAS drives configured as RAID-10 (64 KB stripe size), 4x1 GigE, 1x 10GigE
(optional), and 32GB memory (P/N: 58-00064-001).
•
Chelsio 10 GigE Ethernet adapter (P/N: CH10G0G2-X2). A maximum of one
10GbE adapter is supported per WOS Access Gateway server.
•
Mellanox ConnectX-3 InfiniBand and Ethernet adapter (P/N: MHQH39B-XTR)
with firmware 2.30.3000 used in 10 GigE environments only (InfiniBand is not
currently supported). A maximum of one 10GbE adapter is supported per WOS
Access Gateway server.
Protocols
WOS Access 1.2.5 supports these protocols:
2.3
2.4
•
NFSv3 (TCP only – UDP is not supported)
•
CIFS (SMB 1.0, 2.0, 2.1)
Client Operating Systems
•
NFSv3: All operating systems
•
CIFS: Windows Vista, Windows 7, Windows 8, Windows Server 2008, Windows
1
Server 2012 , and OS X 10.7+
WOS
WOS Access 1.2.5 supports the following WOS configurations:
2.5
•
WOS 1600, WOS 6000, WOS 7000
•
WOS firmware 2.2.2_2. The WOS cluster should be upgraded to this version of
firmware before upgrading WOS Access.
Technology Preview
The following features are provided as a Technology Preview and are not yet
recommended for use in production environments. Full support will be added in a future
release.
•
2.6
NFSv4
Not Supported
Software and hardware and configurations not supported by this release of WOS Access
include the following:
•
NFS v2
•
SMB 3.0
DataDirect Networks
WOS™ Access 1.2.5 Release Notes Revision A0 | 4
•
WOS Access CIFS does not support ‘alternate names’, which provides
compatibility with the 8.3 naming requirements of legacy applications (16-bit
software). [DE2721]
•
WOS Access does not support management using the Microsoft Management
Console from Windows servers. System management should be performed using
the WOS Access Web UI only.
•
SMB Oplocks are not supported. [DE11468, DE2906]
•
NFS over UDP
•
IPv6
•
40GigE
•
InfiniBand (IB)
•
Hardware not certified by DDN for WOS Access
3.0
Installation
3.1
Pre-requisite
This release of WOS Access requires WOS firmware version v2.2.2_2 to be installed and
running on the WOS cluster. Please refer to the WOS Admin Guide for installing or
upgrading WOS. For further assistance on upgrading the WOS cluster, please contact
DDN Support.
3.2
Upgrade
This release of WOS Access supports upgrading from versions 1.2.3 and 1.2.4 of WOS
Access. If you are running a version of WOS Access older than 1.2.3, please contact DDN
Support for assistance with upgrading your system to the latest version. To upgrade WOS
Access, please follow the procedure outlined in the WOS Access Admin Guide.
4.0
Changes Since Last Release
The following product features have been added or modified in this release:
•
Service Relocation now supports two heartbeat interfaces for redundancy. The
Service Relocation configuration page in the Web UI has been updated to support
this feature.
•
The Trashcan feature is now disabled by default on new installations. The setting
on existing installations will not be modified during upgrade. To enable the
Trashcan feature please consult the WOS Access Admin Guide.
•
The following defects noted in previous versions of the WOS Access Release
Notes have been fixed in this release:
DataDirect Networks
o
Files created from NFS are visible as zero length files on CIFS share for at
least 30 seconds and cannot be read from CIFS until written to WOS from
NFS staging. [DE12932]
o
Error messages have been improved for cases where a node fails to join a
synchronization group.
o
The NFS service on the primary node of an SR pair may not be available
after SR is started following the upgrade, even though the service was
started by SR. The Web GUI will indicate that the NFS service isn’t running,
and that it is necessary to restart the NFS service. This isn’t an issue on the
passive node as the NFS service was available on the secondary node after
SR was started. [DE13093]
o
In previous versions of WOS Access, the message “Performance warning:
Export entry is not cached” may have appeared in the NFS log. This
WOS™ Access 1.2.5 Release Notes Revision A0 | 5
indicated that an item in the NFS cache was not found and had to be
retrieved from disk. The message severity has been reduced to DEBUG.
[DE13158]
5.0
Known Issues
The following is a list of known issues in this release of WOS Access.
5.1
Active Directory
•
5.2
Currently, CIFS is not able to update the Active Directory settings on remote
WOS Access nodes in a namespace synchronization group. For these remote
nodes, the Active Directory settings on each node must be updated manually. The
Active Directory manual update procedure is described in the WOS Access
Admin Guide in Section 5.10, “CIFS Service configuration in Active Directory
(optional)”. [DE12189]
CIFS
•
When ABE is enabled on a CIFS export, a directory listing may fail on directories
with more than 25,000 files and/or folders. This is due to the time required to
scan and process metadata for each file and folder before presenting a filtered list
to the user. [DE14812]
•
Workaround: Turn off ABE on the CIFS export configuration.
•
Window Errors not always checked by Windows Applications/clients [DE9443]
If an error occurs while writing from the WOS Access Gateway to WOS core, an
error will be returned to the Windows application running on the client.
However, not all Windows applications check for errors, so an error during the
write may be unnoticed by the application. In order to mitigate limitation with
the Windows applications, WOS Access will do the following:
1) The file will be re-named to
<original_file_name>.<iternal_cifs_file_id>.write_failed. For example:
test_file_4396-6.583681.write_failed
2) On the WOS Access server, the following will be logged in
/opt/ddn/nas/log/wosposix.log:
10/31 00:46:39.448765:|0x7ff0c2b72700|: CRITICAL ERROR:
WOS disconnection detected!
10/31 00:46:39.468524:|0x7ff0c2b72700|: CRITICAL ERROR:
There was a problem saving files to persistent storage
10/31 00:46:39.526776:|0x7ff0c2b72700|: CRITICAL ERROR:
Created file
/mnt/copy/test9/foobar.466552065.write_failed to
indicate write failure
10/31 00:46:39.526806:|0x7ff0c2b72700|: CRITICAL ERROR:
Created file /mnt/copy/test9/foobar1.466552065.write_failed to indicate write failure
•
Using Windows 8 or Windows Server 2012 with WOS Access
By default, Windows 8 and Windows Server 2012 use a feature called Secure
Dialect Negotiation when attempting to connect to a CIFS server. While this
feature is supported by WOS Access it is disabled by default. As such, an attempt
to map a network drive from a Windows 8 client or Windows 2012 server may fail
with the following error:
“An extended error has occurred”
There are two ways to address this issue:
DataDirect Networks
WOS™ Access 1.2.5 Release Notes Revision A0 | 6
1.
Disable Secure Dialect Negotiation on the Windows client by running the
following command from a Power Shell window:
Set-ItemProperty -Path
"HKLM:\SYSTEM\CurrentControlSet\Services\LanmanWorkstat
ion\Parameters" RequireSecureNegotiate -Value 0 –Force
2.
Enable SMB signing on the WOS Access server by running the following
two commands and then restarting the CIFS service:
/opt/ddn/nas/bin/lwregshell set_value
[HKEY_THIS_MACHINE\\Services\\lwio\\Parameters\\Drivers
\\srv] "EnableSecuritySignatures" 0x01
/opt/ddn/nas/bin/lwregshell set_value
[HKEY_THIS_MACHINE\\Services\\lwio\\Parameters\\Drivers
\\srv] "RequireSecuritySignatures" 0x01
•
5.3
5.4
A WOS Access node will remain on the list of the Active Directory domain
machines after the node leaves the domain. This is different from a Windows
node that shows a crossed red marking on leaving the AD domain. [DE2937]
NFS
•
When the amount of data in the WOS Access staging area exceeds 80% of
available capacity, then WOS Access NFS will return an error indicating no more
space is available. This condition will clear after staged data has been flushed to
WOS. If an NFS client has mounted WOS Access NFS without the “sync” option,
then files can still be created but they will be of zero (0) length. [DE14627]
•
The deletion of a large set of files/directories is slow. [DE661]
•
The ls -l <directory> command can take several minutes to complete when the
system is under high I/O load. [DE12037]
Namespace Synchronization
•
A WOS Access gateway node should not be joined to a synchronization group
while members of that group are under a heavy I/O load. The load can lead to
errors that will prevent the gateway node from successfully joining to the group.
[DE14265]
•
Under heavy load, synchronization messages can take a long time to be
distributed to other nodes in the namespace synchonization group. This can lead
to delays in seeing namespace changes at other sites. [DE14030]
•
If a file is being edited on one WOS Access node and, at the same time, the same
file is deleted on another node and the delete event is synchronized with the
group, then the file being edited will remain in the staging area on the first node
and will never be saved to WOS. [DE14350]
Workaround: Manually remove the file from the staging area.
•
A CIFS user, group or share created and immediately deleted on one node may
not always be deleted on the other node. This issue can be worked around by also
deleting the user, group, or share from the other node. [DE4082]
•
The number of directory references may mismatch the actual number of folder
entries if different users create nested files and subfolders in the same folder on
different WOS Access nodes. [DE11010]
Workaround: create or delete the file or folder in the same folder on a different
WOS Access node.
DataDirect Networks
WOS™ Access 1.2.5 Release Notes Revision A0 | 7
•
The system retains the hard link to a file even though different users on different
WOS Access nodes simultaneously deleted the hard link to the same file. [DE9392]
Workaround: try again to delete the hard link.
5.5
5.6
Services Relocation
•
The WOS WebUI pages for languages other than English are not translated to
Services Relocation.
•
During Services Relocation, the WOS Access CIFS users will not be able to access
the mapped share. The I/O will stop and return an error. After the services
relocation process completes (which may take up to two minutes), users will be
able to access the mapped share again.
TrashCan Feature
•
The TrashCan feature does not fully support several advanced operations like
concurrent deletes (and subsequent restores) from different WOS Access nodes
in a Synchronization group.
•
TrashCan support does not currently handle hardlink deletions on NFS file
systems. [DE11408]
•
The TrashCan feature does not have WOS Access WebUI support so it cannot be
enabled or disabled from UI.
DataDirect Networks
WOS™ Access 1.2.5 Release Notes Revision A0 | 8
6.0
Support
Please contact DataDirect Networks Support at any time for assistance. Support can be
reached by these methods:
Web
Support Portal
https://portal.ddnsupport.com
Portal Assistance
[email protected]
Technical Support Bulletins http://www.ddn.com/en/technical-support-bulletins
Email
Support Email
Mailing List Subscriptions
[email protected]
[email protected]
Telephone
DDN Worldwide Directory
http://www.ddn.com/en/support/contact-support
DataDirect Networks
WOS™ Access 1.2.5 Release Notes Revision A0 | 9
World Headquarters
9351 Deering Avenue • Chatsworth, CA 91311
ddn.com
Phone: +1.818.700.7600 Fax: +1.818.700.7601