What’s New in StorNext 5 release 126.96.36.199
Purpose of this Release
StorNext 5 release 188.8.131.52 tightens the integration of applications hosted on Quantum Xcellis Workflow Directors, lowers management complexity and costs, and supports the latest available versions of key operating environments. The new FlexStor licensing options allow storage administrators to use Storage Manager as a service, to better manage data residing in a supported public or private cloud more easily greatly simplifying how cloud storage resources are used. Applications hosted on Quantum Xcellis solutions bring computer resources closer to vital applications, eliminating the need for additional compute servers and network connections.
Note: The Stornext Application Programming Interface (SNAPI) will no longer be supported effective with the next major release of StorNext software. Quantum uses SNAPI to integrate legacy libraries, such as the Scalar i500 and Scalar i40/i80 models with StorNext software. StorNext Web Services is included at no additional charge with StorNext, and provides all of the functionality services by SNAPI.
Note: Advances in disk arrays have made the 32-bit Volume Table of Contents (VTOC) disk labels obsolete. Modern disk arrays use Extensible Firmware Interface (EFI) disk labels capable of supporting physical disks that are larger than 2 TB in size. Beginning with StorNext 5 release 184.108.40.206, VTOC labels are not supported. Prior to upgrading to StorNext 5 release 220.127.116.11, convert arrays that utilize VTOC labels to the EFI format.
To convert arrays that utilize VTOC labels to the EFI format, use the CLI command cvlabel. For additional information about cvlabel, refer to the cvlabel man page in the StorNext 5 Man Pages Reference Guide available online at http://www.quantum.com/sn5docs.
Note: Beginning with StorNext 5 release 18.104.22.168, the StorNext and StorNext FX Xsan Compatibility Guide (part number 6-67068-xx) is deprecated and is no longer maintained. The matrix tables within the StorNext and StorNext FX Xsan Compatibility Guide document are now being maintained in the section titled Xsan Compatibility within the StorNext 5 Compatibility Guide document available on-line at http://www.quantum.com/sn5docs.
New Features and Enhancements in StorNext 5 release 22.214.171.124
Expanded Object Storage
StorNext Storage Manager (SNSM) now has a new storage destination for copies of managed files, in addition to Tape and Object Storage destination. The new destination is known as Object Storage. StorNext 5 release 126.96.36.199 supports multiple Object Storage providers and media types. The StorNext 5 User’s Guide (Chapter 12: Object Storage) provides information on the new storage destination functionality, and information on how to configure the new Object Storage providers and media types. The information is also available in the StorNext 5 Online Help.
FlexStor for Public Cloud allows end-users to connect their Amazon Web Services or Microsoft Azure managed cloud service accounts to StorNext Storage Manager. The StorNext 5 Licensing Guide provides information on the new subscription-based StorNext Storage Manager Subscription (FlexStor) license, in addition to the new procedure for importing StorNext licenses.
Improved Capture State
The collection of logs and snapshots has been automated so that all of the important information needed to quickly triage problems can be gathered and sent to Quantum Support with a single button. The StorNext 5 User’s Guide (Chapter 8: Service Menu Functions) section Capture State provides information on how to create a log file that captures the current state of your system, and automatically upload the log file to Quantum Support. The information is also available in the StorNext 5 Online Help.
Enhancements to StorNext File Permissions
StorNext 5 release 188.8.131.52 has expanded support for Access Control Lists (ACLs). Depending on the system configuration:
- ACLs are now supported for native StorNext Linux clients.
- ACLs are now supported over NFS when using StorNext appliances as NFS servers.
StorNext 5 release 184.108.40.206 also adds support for Unix permission bits on Windows clients. With these changes, StorNext now offers users a choice in cross-platform security models that support more consistent file system permissions for environments containing diverse StorNext client types. The StorNext 5 User’s Guide (Appendix F: Security) section StorNext Security provides information on considerations when selecting a security model, access-checking functionality and configuring identity mapping.
Password Policy Enhancement
Enhancements have been implemented to support the configuration and use of strong passwords within your password policy. The StorNext 5 User’s Guide (Chapter 7: Tools Menu Functions) section UserAccounts provides information on how to modify the password policy. The information is also available in the StorNext 5 Online Help.
New Dynamic Application Environment (DAE) for Xcellis Workflow Director
The StorNext 5 User’s Guide (Chapter 7: Tools Menu Functions) section Dynamic Application Environment provides information on how to display the current status of your virtual machine environments. The information is also available in the StorNext 5 Online Help.
Fixed Issues and Enhancements Addressed in StorNext 5 release 220.127.116.11
|Operating System||Change Request Number||Service Request Number||Description|
|An issue was fixed to inform to call Quantum Support if File System expansion operations failed in the GUI. This fix allows users to perform the appropriate File System expansion steps.|
|An issue was fixed where the cvupdatefs utility failed to add stripe group with mis-matched size disks.
The cvupdatefs utility can add a stripe group to a file system. When doing so, the utility checks to make sure that all disks are the same size. If some disks are larger than others, the file system can only use the space on each disk equal to the smallest disk in the stripe group. The remaining space on the larger disks is wasted. The utility prints out a warning in this situation, indicating how many bytes of disk storage would be wasted if the operation is allowed to proceed. If the administrator chooses to proceed, the issue resulted in the failure of the operation and the stripe group was not added to the file system.The fixed issue allows the operation to go forward and successfully add the stripe group.
|All||60964||3546218||Enhancements were made to the sncompare utility to log meaningful error messages for the following two conditions
rather than core dumping, or getting into an infinity loop:
|All||61045||3719554||An issue was fixed where some StorNext perl scripts using /usr/adic/perl/bin/perl where calling /usr/bin/perl and failing if the Data::Dumper Perl module was not installed for the operating system provided Perl package. The impacted scripts now explicitly use the Quantum Perl package which provides the Data::Dumper module.|
|All||61719||3641476||The fsfileinfo command now ensures that it will not insert database values that interfere with the functionality of the fsclean command.|
|All||61788||3581062||An issue was fixed to reduce downtime duration when upgrading from releases prior to StorNext 5 by deferring pending RPL
|All||61862||3600240||The mechanism used to launch and track distributed data mover processes had some flaws and weaknesses that could cause
failures or unnecessary retry operations and a delay or inability to store or retrieve storage manager files. An issue was fixed to clean-up the internal communication so that the operation is more robust and that if errors do occur, the correct error is
reported to the administrator.
|An issue was fixed in the policy request code to better utilize all available drives.|
|All||62201||3636874||An issue was fixed to prevent authenticated users from injecting nefarious SQL commands on certain GUI pages. This fix
improves application security.
|All||62202||3636874||An issue was fixed to prevent authenticated users from injecting nefarious scripts on certain GUI pages. This fix improves
|All||62203||3636874||An issue was fixed that to allow administrative users to define and set a more restrictive password policy for GUI users. This
issue improves application security.
|All||62204||3636874||An issue was fixed to prevent authenticated users from injecting nefarious scripts on certain GUI pages. This issue improves
|All||62206||3636874||An issue was fixed to prevent authenticated users from injecting nefarious hyperlinks on certain GUI pages. This issue improves application security.|
|All||62208||3636874||An issue was fixed to prevent GUI error messages from revealing private application information. This fix improves application security.|
|All||62422||n/a||An issues was fixed to allow an Object Storage delete request to timeout in order to prevent processing hangs.|
|All||62454||3701100||An issue was fixed where asynchronous web services may not be able to start following an upgrade from pre-StorNext 5 release 5.3.0 due to the wsar agent temporary directory not being created on upgrade.|
|All||62529||3668020||An issue was fixed to support directory names containing spaces when defining File System Quotas. This fix allows
directory names to contain spaces when defining File System Quotas.
|All||62560||3644724||An issue was fixed to allow StorNext to ignore Spotlight server requests for inode zero in order to avoid filling the system log
with error messages.
|All||62561||3667834||Enhancements were made to replace the $VS_DIR string, if it exists, with the real value in the
/usr/adic/MSM/internal/config/config_file_<archivename> files. The enhancements allow MSM to start without requiring manual intervention.
|All||62797||3680596||An issue was fixed to more accurately track file modification time to ensure files are stored.|
|All||62814||3658950||An issue was fixed where incorrect errors were being generated when a process doing a BulkCreate received a signal.|
|All||62815||3676584||An issue was fixed to improve error handling for the fsfileinfo Web Service call. This fix allows the fsfileinfo Web Service call to properly report Web Service errors.|
|All||62850||3677566||The WSAR daemon was incorrectly allowing open files to be passed down to the commands it was starting to fulfill web
services requests. When the WSAR was restarted, the existence of one or more of those command programs precluded
opening the socket port that WSAR needs for communication across the network. The WSAR program was changed to close
open files when starting those commands.
|The FSM process dies unexpectedly with the error stripe/X length Y block/Z – Detected bad metadata contents on disk! ; however, running the command cvfsck detects no inconsistent metadata. The FSM process has been fixed so that the race condition that leads to the problem no longer occurs.|
3669114, 3670060, 3689402
|An issue was fixed to prevent the StorNext file system from incorrectly generating a RAS ticket indicating that the metadump’s inode count is incorrect and needs to be rebuilt.|
1608112, 1611896, 1614798
|Enhancements to StorNext file permissions have been implemented.|
1608112, 1611896, 1614798
|Enhancements to StorNext file permissions have been implemented.|
|All||63059||3680048||An issue was fixed to prevent an FSM restart containing the ASSERT message:open_check() hits ASSERT((op->open_flags &OPEN_FREED) == 0) for ASR helper inode|
3692128, 3697776, 3701602
|An issue was fixed to prevent the StorNext file system FSM from crashing when a client attempts to access a deleted file or directory.|
|All||63095||3683190, 3682876||An issue was fixed to correct the suggestions in error messages which contain suggestions for re-invoking the cvupdate and cvmkfs commands with additional or changed command line options.
The cvupdate and cvmkfs utilities issue certain error messages which contain suggestions for re-invoking these
|All||63133||3680048||An issue was fixed to prevent an FSM restart containing the ASSERT message:open_check() hits ASSERT((op->open_flags &OPEN_FREED) == 0) for ASR helper inode|
|All||63149||3683912||Path names with lengths that exceed 1023 characters fail to store, and are listed in an Admin Alert. All store candidates that have full path names with lengths less than or equal to 1023 characters store correctly. Store candidates that have path names with lengths greater than 1023 characters fail to store, and an Admin Alert listing the failed file paths is sent, so that an Administrator can take corrective action for each file (likely by renaming each file to a path whose length does not exceed the 1023 character maximum allowed).|
|All||63210||3686758||The fsaddrelation command no longer unmounts the target file system, thereby allowing it to execute faster.|
|All||63263||n/a||An issue was fixed with the Disk Licensing Status (DLS) report generation to include reports from both nodes of a High
Availability (HA) system on Red Hat Enterprise Linux (RHEL) 7 systems.
|All||63348||n/a||StorNext now prevents a kernel panic when a process running an unmount receives a signal.|
|All||63374||3692674||If the FSM process is restarted for any reason (for example, a fail-over occurs), some clients may fail to reconnect. The
StorNext reconnect processing has been re factored to avoid the failure.
|All||63382||3692674||Incorrect error handling in the FSM may cause attribute updates to be delayed, resulting in stale file attributes being seen on some clients. The StorNext code path in the FSM process that was returning the wrong error code has been corrected.|
|The fsmedcopy and fsclean commands now perform additional up-front validation to ensure media file count integrity.|
|An issue was fixed to prevent Supervisory Mode AccessProtection (SMAP) from being disabled.
Recent improvements in computer chip technology have allowed SMAP functionality to be enabled by host operating
systems. A combination of this newer technology and a recent update to Red Hat Linux exposed an improper use of access to user data by the StorNext driver. This resulted in a Linux kernel panic as soon as the StorNext services were started. A workaround was released, disabling SMAP.
|An issue was fixed to update the StorNext metrics Web Service data format to prevent repetitive warning logging statements. This fix keeps the snapshot catalina.log file from growing too large.|
|All||63911||3706086||An issue was fixed to prevent an unlikely MDC restart when using affinities, autoaffinities, and running low or out of space for an affinity.|
|All||64098||3712782||An issue was fixed to support Unicode characters in asynchronous web-service calls. This fix allows filenames
containing Unicode characters to display properly when using asynchronous web-service calls.
|All||64106||n/a||The fschfiat command now fails if the -A y option is specified for a file with an associated policy class that does not
have Alternate Store Location (ASL) enabled.
|All||64205||3716838, 3714266||An issue was fixed where GUI images were not able to be seen on Internet Explorer versions 9, 10, and 11.|
|All||64527||3725120||Executing the command fsclean -c <classid> cleans files associated with that class on all Object Storage and
Storage Disk (SDISK) media even when those media are not directly associated to that class. Tertiary Storage Manager
(TSM) used to clean Object Storage and SDISK media for fsclean -c <class> only when the media were directly
associated to the class. Those media that contain files stored for all classes were not cleaned. In this release of StorNext, media that contain files for all classes are now cleaned for those files associated with that class.
|All||64606||3728212||An issue was fixed to provide a better description of the conditions at the client node and includes the file system name.
A client node with an active file system mount remains connected to the file system service (file system manager process) for that file system. If the connection is interrupted, the client attempts to reconnect. Certain conditions such as deleting the file system would cause this service to be terminated. The existing error message did not communicate the situation clearly to the administrator.
|All||64615||3729026||The Alternate Store feature dependency on having a file system with an assigned device key equal to one (1) has been removed.|
|All||64728||3733640, 3729298||An issue was fixed that resulted in an MDC restart due to handling of a recent MDC restart or client reconnects. This issue was uncovered due to network trouble with frequent client reconnects.|
|All||64810||3732456||Alternate Store Location (ASL) configuration and status information was added to the set of information collected by
pse_snapshot . The following commands are run to collect that information:
|All||64819||3732456||The Alternate Store service is now able to recover and reconnect after a prolonged network outage between the local and remote sites.|
|All||64879||3733640, 3729298||An issue was fixed that resulted in an MDC restart due to handling of a recent MDC restart or client reconnects. This issue was uncovered due to network trouble with frequent client reconnects.|
|All||65008||3733390, 3724758, 3729298||An issue was fixed to remove connections from the poll mask when closing the them. When the handler for connections prior to activation exceeds 512 connections, it discards them, but leaves them in the mask used to poll for socket activity on the main listener thread. This causes that thread to spin on a CPU for the lifetime of the FSM.|
|All||65126||3741040||When invalidating stranger media copies, the fsrmcopy command now clears the FS_STANGER_MEDIA attribute flag from both the on-disk attributes and the database attribute entries associated with the file.|
|All||65167||3741040||An issue was fixed where a retrieve from stranger media ensures that all data has been flushed to a disk before returning a successful status.|
|All||65168||3741040||Beginning with StorNext 5 release 18.104.22.168, the dm_util command has been enhanced to support modification of the FS_STRANGER_MEDIA flag setting in the on-disk attributes of a file.|
|Linux||32315||1197476||An Admin Alert is now sent when a policy class hard limit or soft limit is reached. In the past, whenever a policy class
reaches its hard limit or soft limit, Tertiary Storage Manager (TSM) would not provide any notification that a limit had been reached. TSM now sends an Admin Alert when either the soft or hard limit is reached.
|Linux||63062||3682876, 3644738, 3666256||An issue was fixed to display the correct and meaningful StorNext GUI error message.
A check was added to cvupdatefs and cvmkfs such that when a file system was being expanded or created, the label on each new LUN was compared with the label on existing LUNs in all active file systems in the cluster. If a match was found, it was likely that a disk was about to introduced into a file system that was already present in a running file system. If these commands were issued from the CLI, the error message was displayed correctly to the administrator. However, when these commands were run using the StorNext GUI, the error message was not being returned correctly to the GUI, resulting in a meaningless error displayed by the GUI to the administrator.
|Linux||63660||n/a||An issue was fixed to allow support for case insensitive mounts on Linux for Samba.|
|Linux||64066||n/a||ASL remains enabled when moving an ASL enabled file to a non-ASL-enabled directory|
|Linux||65050||3733306||Enhancements have been made to error messages generated when a few specific metadata consistency problems are
|Windows||62216||3656984||An issue was fixed with the StorNext Windows driver to use the correct calls to the Windows operating system which allows access to files that are created with special characters outside of the standard set of ASCII characters.
Special characters are characters outside of the standard set of ASCII characters and are created to allow file names and paths to appear in native languages. Some characters worked, such as German vowels, but others, such as Chinese logograms, would fail to be manipulated correctly. The StorNext file system supports these characters in file names and paths. However, the StorNext file system implementation on Windows used an older version of the interaction with the operating system which resulted in the inability to open or access files containing these characters.
File System Server: Server Revision 22.214.171.124 Build 67222 Branch branches_126.96.36.199 BuildId E Built for Linux 3.10.0-121.el7.x86_64 x86_64 Created on Thu Nov 10 19:57:18 MST 2016 Built in /scm/nightly/VM-0-RedHat7-x86-64-SP0/sn/buildinfo File System Client: Client Revision 188.8.131.52 Build 67222 Branch branches_184.108.40.206 BuildId E Built for Linux 3.10.0-121.el7.x86_64 x86_64 Created on Thu Nov 10 19:57:18 MST 2016 Built in /scm/nightly/VM-0-RedHat7-x86-64-SP0/sn/buildinfo Host OS Version: Linux 3.10.0-327.36.3.el7.x86_64 #1 SMP Thu Oct 20 04:56:07 EDT 2016 x86_64