CIFS/NFS Gateway Product Release Notes. Version May 2015 Revision A0

(1)

CIFS/NFS Gateway

Product Release Notes

(2)

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.

DataDirect Networks, the DataDirect Networks logo, DDN, DirectMon, EXAScaler, GRIDScaler, HScaler, IME, Infinite Memory Engine, Information in Motion, In-Storage Processing, NAS Scaler, NoFS, ObjectAssure, ReACT, SFA, SFA 10000 Storage Fusion Architecture, SFA10K, SFA12K, SFX, Storage Fusion Architecture, Storage Fusion Fabric, Storage Fusion Xcelerator, SwiftCluster, WOS, the WOS logo 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.

(3)

2.0 Changes in this Release

The following new features, functional changes and defect fixes are included in this release of the CIFS/NFS Gateway.

2.1 New Features

The following new features are included in this release:

• The CIFS/NFS Gateway now supports the NFSv4 protocol. Shares can now be accessed using

both NFSv3 and NFSv4. NFSv4 ACLs are fully supported and will be respected by NFSv3 and SMB/CIFS clients and vice versa. Note that not all features of the NFSv4 protocol are currently supported. See the Known Issues section below for more details.

• In addition to Active Directory UNIX attributes and manual mapping, LDAP servers can now

be used as an ID mapping source.

• Local groups can now be modified to include both local and domain users and groups.

2.2 Functional Changes

The following functional changes are included in this release:

• NFS version support can now be specified when creating or modifying a share. A share can be

configured to support NFSv3, NFSv4, or both versions. Shares will always support SMB/CIFS access.

• The nasctl user and group commands now support searching LDAP servers for user/group

information.

• ID mapping priority between Active Directory and LDAP can now be configured using the

“mapping-priority” option of the nasctlcluster_setconf command.

• The NFSv4 default domain name can be specified using the “nfsv4-id-domain” option of the

nasctl cluster_setconf command.

2.3 Defect Fixes

Fixes for the following defects are included in this release:

• Zero-byte files created when trying to save file from MS Office 2010 or 2013 [SR35933][DE16844]

• GPFS mmshutdown command does not stop NFS/CIFS services [DE8504]

• Short period of time where NFS share access options are not propagated across cluster

[DE16877]

• Cluster becomes UNHEALTHY if NFS access options contain at least 257 host addresses

(5)

3.0 Installation

The CIFS/NFS Gateway software is compatible with the following DDN products:

• DDN GRIDScaler (version 2.1.1 and above)

The Gateway software will be installed by default on the above products – no additional installation is required.

3.1 Upgrade

Follow the steps below to upgrade an existing installation of the CIFS/NFS Gateway software:

1. Stop services on all nodes in the Gateway cluster by running the following command:

nasctl cluster_stop –a

2. Unpack the product tarball on each node in the cluster. This will create a directory named

“RPMS” containing the Gateway software packages.

3. From the RPMS directory on each node in the Gateway cluster, run the following command to

upgrade the Gateway software packages: rpm –Uvh *.rpm

4. Restart Gateway services on all nodes in the cluster by running the following command:

nasctl cluster_start –a

4.0 Known Issues

The following are known issues with the CIFS/NFS Gateway software:

• DDN NFS and GRIDScaler cNFS cannot be enabled on the same cluster node. To disable DDN

NFS on a node, use the nasctl nfs_stop command.

• File locking is not supported by DDN NFS in this release. NFS clients that attempt to lock a

file will receive an I/O error.

• The following features of NFSv4 are not supported in this release:

o Authentication mechanisms other than SYS_AUTH (such as AUTH_DH, Kerberos,

LIPKEY, and so on)

o Volatile file handles

o File locking

o Delegations (client-side caching)

• Standard Linux NFSv4 ACL tools cannot work with user or group names that contain spaces.

The default ACL on new shares in the CIFS/NFS Gateway contains a group named “Local Admins”. To edit this ACL, use the Windows ACL editor via CIFS.

• When an ACL is edited using NFSv4 tools from Linux, the order of ACEs may not be preserved

in a way that Windows expects, resulting in error messages such as “The permissions on

[filename] are incorrectly ordered, which may cause some entries to be ineffective." When working in cross-protocol environments, ACLs should be edited via Windows to preserve maximum compatibility between protocols.

(6)

• CIFS share modes are not supported by GPFS. Customers that require concurrent file system access from both CIFS and GPFS must use byte-range locks for access synchronization.

• File permissions should not be modified on GPFS directly using chmod, chown, and so on.

These commands may modify or completely remove ACLs on files or directories that are required for proper CIFS functionality. Permissions should be modified via CIFS or NFS clients instead.

• Local group names with non-ASCII characters are not supported. [DE5234]

• The CIFS server does not support management using the Microsoft Management Console from

Windows servers. System management should be performed using the nasctl command-line tool only.

• When the Gateway cluster is removed from an Active Directory domain by an outside source

(that is, by deleting the Gateway computer object on the AD controller), the nasctl command “ad_show” may still incorrectly report the cluster as being joined to the domain. Use the

“ad_reload” command to refresh domain state on the Gateway cluster. [DE6180]

• SMB change notification is not supported. Changes made to a file system either from other

protocols or from other nodes will not be relayed to SMB/CIFS clients. [DE6875]

• DDN NFS does not support the creation of FIFO devices. [DE8141]

• DNS records on the Active Directory domain server will not be automatically updated when a

cluster is joined to the domain. DNS records must be updated manually. [DE8718]

• In the event that multiple file systems are shared, a single GPFS file system going offline on a

node may not trigger VIP failover. Failover will only occur when the file system with the cluster lock file (as configured using the nasctl cluster_create command) goes offline. Otherwise, the node will continue to serve NFS and CIFS requests. However, any requests

directed to the offline file system will return an I/O error. [DE9835]

• The CIFS server does not support durable file handles. As a result, node failover events that

occur during CIFS file operations will require a restart of the CIFS transfer. For example, on

Windows File Explorer, this would require a file copy to be canceled and restarted. [DE9837]

• By default, GPFS limits the number of concurrent byte-range locks on a file to 200. Any

attempt to lock a file that has hit the lock limit will fail. This value can be changed on GPFS

(7)

5.0 Support

NOTE: When requesting support on GRIDScaler systems, please run

/opt/ddn/gs/scripts/gs_showall.sh on the subset of nodes with problems and NSD servers. Send the generated output to DDN Support for analysis. You will find complete

instructions for the gs_showall.sh command in the GRIDScaler Admin Guide.

Please contact DDN Technical Support if you have questions or require assistance. Support can be reached at any time by phone, by email, or on the web.

Web

Support Portal https://community.ddn.com/login

Portal Assistance [email protected]

Telephone

DDN Worldwide Directory http://www.ddn.com/support/contact-support

Email

Support Email [email protected]

Bulletins

Support Bulletins http://www.ddn.com/technical-support-bulletins

End-of-Life Notices http://www.ddn.com/support/end-of-life-notices

Bulletin Subscription Requests [email protected]

(8)

CIFS/NFS Gateway Product Release Notes. Version May 2015 Revision A0

CIFS/NFS Gateway

Product Release Notes

Table of Contents

2.0

Changes in this Release

2.1

New Features

2.2

Functional Changes

2.3

Defect Fixes

3.0

Installation

3.1

Upgrade

4.0

Known Issues

5.0

Support