Change Requests: Notes and Fixed Issues

The following tables present notes and fixed issues for StorNext NAS 1.4.0.x.

Table 1: StorNext NAS 1.4.0.3
Change Request

Description

H1679

FIXED

In some environments, smbd can panic when multiple nodes are placed into a NAS cluster.

This issue has been resolved with H1715 listed below.

H1715

FIXED

To address the CVE-2017-7494 security issue (commonly referred to as SambaCry) and smbd panics, Samba libraries have been patched. This patch is part of the 1.4.0.3 upgrade package.

H1732

FIXED

Under certain circumstances, the workaround addressed in H1648 for the SambaCry vulnerability was overly restrictive, which prevented access to SMB shares for macOS clients.

This issue has been resolved with H1715 listed above.

H1734

FIXED

If keepalived unexpectedly fails, the mater node's VIP could be orphaned when the master node transitions to BACKUP state.

The controller has been updated to clean up the node's orphaned VIP.

Table 2: StorNext NAS 1.4.0.2

Change Request

Description

H1648

NOTE

To address the CVE-2017-7494 security issue, the SMB option nt pipe support=no has been added to the StorNext NAS global SMB Options.

H901

FIXED

In the following scenario only, NAS services will not failover when the StorNext file system is stopped:

  1. The StorNext FSM is running on the same node as the NAS master node.
  2. NAS has been enabled an Xcellis Workflow Director system.
  3. NAS failover has been enabled on NFS shares.

NAS services have been updated to appropriately failover when the StorNext file system is stopped.

Note: NAS failover is supported only on the Xcellis WFD (CentOS7) for NFSv4 clients. For environments exporting NFS shares on Xcellis WFD or G300 gateways, or on Artico or MDC servers, clients connect to the shares through the master StorNext NAS System static IP address.

H1416

FIXED

In certain scenarios, such as when the network cable is disconnected from a Quantum appliance, NAS shares remain inaccessible when the network connection is reestablished.

The controller has been updated to remount NAS shares after a network connection is reestablished.

H1509

FIXED

All SMB options — even those that are case sensitive — were being converted to lowercase when they are written to the smb.conf file.

The controller has been updated to respect case-sensitive settings when writing SMB options to the smb.conf file.

Table 3: StorNext NAS 1.4.0.1

Change Request

Description

N/A

FIXED

In the StorNext NAS 1.4.0 release, the blocksize used in Samba’s virtual file system (VFS) was not compatible with StorNext. This incompatibility caused a file’s size on disk calculation to be incorrect. In addition, it can cause Windows 7 clients to crash when accessing large files in NAS SMB shares.

StorNext NAS 1.4.0.1 has corrected this issue.

  • If you are currently running StorNext NAS 1.4.0, make sure to upgrade to StorNext NAS 1.4.0.1 to avoid this issue.
  • If you are currently StorNext NAS 1.2.5 or 1.3.0, you can upgrade directly to StorNext NAS 1.4.0.1.
Table 4: StorNext NAS 1.4.0

Change Request

Description

66235

NOTE

When generating the krb5.conf file, the dns_lookup_kdc option was always set to false.

Quantum Support can now alter this setting by changing a Registry Key value. See AD Forest Tips and FAQs.

66237

NOTE

In some Microsoft AD environments, you may need to exclude or ignore specific trusted domains, such as those that are behind firewalls. See AD Forest Tips and FAQs.

63682

NOTE

The NAS controller can now detect StorNext case insensitivity settings and reset SMB share case sensitive options accordingly. See SMB Share Options. .

66228

FIXED

During a reboot or upgrade, the StorNext NAS controller attempts to join/rejoin to the AD server, even in cases when configuration settings have not changed and the node is fully functional.

During reboot or upgrade, the StorNext NAS controller now checks if configuration has changed before attempting a rejoin.

66234

FIXED

The StorNext NAS controller was not checking Access Control Lists (ACLs) before moving files to a directory.

The controller has been updated to check ACLs prior to moving files to a directory.

66236

FIXED

In certain scenarios, notably when there exists a network or DNS related issue, the StorNext NAS controller delays starting. This delay can cause systemd to restart the process, resulting in a restart-loop.

By increasing the timeout limit to 300 seconds, systemd restart-loops are now avoided.

66239

FIXED

In a NAS cluster, non-master nodes are issuing commands to bind to a Microsoft AD environment, which can interfere with the master node's processes.

The controller has been updated to skip certain commands on non-master nodes.

66295

FIXED

In certain scenarios, winbind checks are being executed only once, causing the check to fail due to timeout or communication issues.

StorNext NAS now executes winbind checks multiple times before reporting a failure.

66297

FIXED

In certain scenarios, when binding StorNext NAS to a Microsoft (AD) environment, you may need to specify multiple Kerberos domain controllers.

You can now specify multiple domain controllers with the auth config ads command. See Apply AD Authentication To NAS.