What's New in StorNext 7.2

Purpose of this Release

The StorNext 7.2 release provides new features and enhancements, and also provides software fixes listed in the section Fixed Issues and Enhancements Addressed in StorNext 7.2.

This release also includes a significant upgrade to the underlying operating system of the Quantum appliances; specifically, the operating system is upgraded to Rocky 8.7 from CentOS 7.9.

Note: Upgrades are only allowed from StorNext version 7.1.0 (or later) to StorNext version 7.2.0.

Important Information about StorNext Xcellis systems connected to F-Series and H-Series RAIDs using iSER

A performance issue exists with StorNext version 7.2.0 Xcellis appliance platform when storage targets are configured with iSCSI RDMA (iSER). The issue can cause a significant degradation in performance as compared to previous releases of the StorNext 7 Xcellis appliance platform and only affects StorNext Xcellis systems connected to F-Series and H-Series RAIDs using iSER. Customers configured with NVMe-oF RDMA, NVMe-oF TCP, iSCSI TCP, or Fibre Channel storage targets are not affected by the issue and can be safely upgraded. If iSCSI RDMA (iSER) is configured, and (a) an upgrade to StorNext version 7.2.0 is required and (b) your environment contains an F2100 system, Quantum recommends you contact Quantum Support (see Contacting Quantum Support) for a software patch before you upgrade to StorNext version 7.2.0.

Information about Pre-Upgrade Checks

Beginning with StorNext version 7.2.0, the pre-upgrade check validation process also checks for RPM files that cannot be upgraded. Upon validation failure, an Admin Alert containing a list of RPMs found that are not expected on the node(s), is generated. You must manually remove these RPMs from the node(s) before you activate the upgrade. If the system you are upgrading includes the lin_tape RPMs, you must manually remove the RPMs before you start the upgrade process, and then install the RedHat 8 version of the RPMs after the upgrade process is complete.

Information About StorNext Unified Connector Upgrades

If your system is running StorNext version 7.1 (or later), you must upgrade the StorNext Unified Connector on non-MDC based clients.

Note: The StorNext Unified Connector is automatically upgraded on MDC based clients as a part of the StorNext software upgrade process.

Caution: Only the latest version of the StorNext Unified Connector properly displays performance metrics and statistics in the UUI.

To upgrade your StorNext Unified Connector, see Unified Connector Tasks.

Information About StorNext Firmware Upgrades

If your system is running StorNext 7.0.1.1 (or earlier) and you use the StorNext GUI to upgrade your firmware, do the following to upgrade to StorNext 7.0.2 (or later).

Caution: Due to a known file size limitation, if you attempt to upgrade your firmware using the StorNext GUI, the upload of the second firmware file fails with the following error:

File upload failed. The request was rejected because its size exceeds allowed range.

Do the following to workaround this issue:

  1. Modify the com.icesoft.faces.uploadMaxFileSize parameter in the web.xml file (located in /usr/adic/tomcat/webapps/ROOT/WEB-INF/web.xml) to a value of 10737418240.

    Example

    <!--  Max. file size to upload (10 GB)  -->
<context-param>
<param-name>com.icesoft.faces.uploadMaxFileSize</param-name>
<param-value>10737418240</param-value>
</context-param>

  2. Save your changes to the web.xml file.

  3. Open a root UNIX shell window on your appliance, and run the following command to restart the StorNext GUI:

    Note: Wait a few minutes before you try to access the StorNext GUI, and then retry the command if it fails.

    # service stornext_web restart

New Operating Systems Supported Effective with StorNext 7.2

Operating Systems No Longer Supported Effective with StorNext 7.2

New Features and Enhancements to the Quantum Unified User Interface (UUI)

Features No Longer Supported Effective with StorNext 7.2

Information about FlexSync Support

StorNext 7.2 only supports FlexSync 3.1.0 (or later). If you want to install StorNext 7.2 on your system, or upgrade your system to StorNext 7.2 and want to use FlexSync, then you must install FlexSync 3.1.0 (or later), or upgrade to FlexSync 3.1.0 (or later) on each system using the feature, including the source destination, the target destination, and the managing appliance.

Caution: Mixed versions of FlexSync daemons is not supported and results in a communication error. You must install the same version of FlexSync, or upgrade to the same version of FlexSync on all of the hosts or systems using Flexsync. A newer version of the Flexsync daemon cannot communicate with an older version within a configuration, or on another host or system.

Compatibility and Support

The StorNext 7.2 Compatibility Guide provides the basic compatibility for StorNext 7.2, including the StorNext components supported, operating systems and service packs, libraries and drives, browsers, virtual machines, and appliance support. Listed below are just a few of the types of information available to you in the StorNext 7.2 Compatibility Guide.

Fixed Issues and Enhancements Addressed in StorNext 7.2

ID Description
SNXT-122 fslocate -k file_key fails on some files in mdarchive query
SNXT-139 Improve fsmodclass & fsexpcopy man pages to include info about rebuild candidate list
SNXT-179 Persistent LOG_INFO message in query_ldap() routine produces a large number of entries in /var/log/messages
SNXT-193 sgadd: when --template used for stripe group with exclusive affinity, sgadd issues an error message and exits: *Error*: You must specify data, metadata, or both
SNXT-194 cvadmin -H remote_host -e \"disks refresh\" do not trigger on remote_host but on local_host
SNXT-195 cvadmin -H remote_host -e \"disks\" reports wrongly \"Disks known to FSMPM on host \"local_host\"\" instead of \"remote_host\"
SNXT-210 TSM recreate tape: misleading error messages , e.g. Some files could not be recreated from alternate media due to segment size mismatches with source media
SNXT-317 Dynamic Library Pooling ( DLP ) doesnt cope well when one library of the DLP Pool runs out of available media
SNXT-335 Storage Manager Restore Procedures: missing crucial tips and warning for pitfall
SNXT-377 fsretrieve can error when object are pulled back from archive tier to cool tier
SNXT-390 A tiering job or policy should default to only affect files
SNXT-446 Fsmpm has sigabort due to accept failure in libevent code
SNXT-457 zombie fsprobe processes pile up on MDCs due to file descriptor leak in parse_json_cli()
SNXT-475 Bug 78307 - modified files that are removed before being re-stored cannot be recovered
SNXT-493 fsmedcopy recreate fails indicating there are no files to copy when there are.
SNXT-536 snprobe -a can stall in environments with large numbers of DLC connections
SNXT-581 sncompare causes false positive with SDISK and Tape Copy will suggest to remove ALL_COPIES made on All Entries
SNXT-594 fsmedcopy reconciliation to help with - Deleting file during store causes database to show endtime as active.
SNXT-602 cvupdatefs() should not run 'sn_dmap -c' on LUN's that have been upgraded from "Short Labelled"
SNXT-620 XWE Gateway Agent is sending invalid file system metrics for MDC file system when affinity/tiering is enabled
SNXT-643 Fsm Assert Panic - ASSERT failed "!set || (rptr->iref_flags & IREF_RETURN_ATTRS) == 0
SNXT-661 CCTL logs flooding the nssdbg
SNXT-670 snaccess test functions incorrectly states subdirectory access is allowed
SNXT-678 Bug 73290 - File specific xrep error should not fail entire mover request seen on a XWD running SN7.0.3
SNXT-684 (CVE-2023-1945) - firefox-91.13.0-1.el7.centos - Unexpected data returned from the Safe Browsing API could have led to memory corruption and a potentially exploitable crash.
SNXT-685 add mechanism to disable hardcoded mover obj store retry logic
SNXT-688 (CVE-2022-37434) zlib: heap-based buffer over-read and overflow in inflate() in inflate.c via a large gzip header extra field
SNXT-693 (CVE-2023-0767) NSS Tools nss: Arbitrary memory write via PKCS
SNXT-694 escaped chars can lead to >255 name file,silently preventing store, failing policy involving subsequent candidates
SNXT-705 7.1.1 upgrade rendered Mellanox Infiniband devices undetectable.
SNXT-714 Compatibility Guide - Support for IBM TS4300 + IBM LTO 9 HH Fibre channel drives
SNXT-731 snstatd appears to leak memory
SNXT-734 /opt/DXi/scripts/collect-local: line 557: /usr/bin/pg_dump: No such file or directory
SNXT-740 transcribe operation to LTFS tape varies media to suspect if the destination media reach EOT/EOM
SNXT-766 cvfsck -E "FS" fails and coredump if "FS" has vacant SG
SNXT-768 fsexport -b cannot copy contents from LTO to LTOW (WORM) Media
SNXT-774 Without "exec" and "suid" XML tags in nss_cctl.xml, the values are set to false by default
SNXT-775 Man page update cvfsck -A only showing results in read/write mode
SNXT-819 ConvertAllRsvdExtents() triggers: PANIC: "BUG: unable to handle kernel NULL pointer dereference at 0000000000000004"
SNXT-878 Bug 76850 - FSM selecting a Remote NDIS Compatible Device causing connection issues (Clients interlocking becasue registered with same internal IP)
SNXT-881 Schema update failure when upgrading from SN pre-5.2.0 to post 6.4.0 in 7.1 code
SNXT-891 Documentation: Update the text for "Online" library action to reflect that it updates the device path and the mailbox slot count
SNXT-912 Documentation: Need to document when dbupgrade is run and what changes are being made to avoid unexpected downtimes or delays during Firmwareupgrades
SNXT-937 sntier - Make sizes human readable and clarify what is meant by size in sntier command outputs. It is incredibly difficult to keep translating numbers like 47398723478732348 into terabytes or how many “seconds old” something is
SNXT-946 tiering - not enough info provided when a job failed due to estimate bigger than free space in pool
SNXT-956 Tracking Bug: Radar 119052712 Xsan clients fail to mount at boot
SNXT-1005 CVFS Client is leaking kmalloc-96 objects
SNXT-1019 Segmentation Fault in sn_dirent_key_init dir_btree.c:79
SNXT-1062 CVFS PANIC: _cvRelLock: unlocking a non-locked lock
SNXT-1116 /usr/adic/PSE/bin/query_tape_libraries is missing suspect count in output
SNXT-1215 Autodesk Flame fails to render DPX file with error Bad Addres
CON-10602 MDC node with tiering recently disabled still shows the 'Pools' feature, which is confusing to customers
CON-10604 Unified Connector - Alma 8.7 and Rocky 8.7 are not supported by UC - minimum is 9
CON-10619 StorNext 7.1 + UUI/USBE/API GW 7.1.1: 500 error on Alerts page when with any action
CON-10689 MacOS Unified Connector Package installer is blocked because it is not from an identified developer
CON-10701 Metrics page is not displaying graphs and statistics due to exceeding qustats data length
CON-10737 Adding second separate MDC node or HA pair pointing to same FS name server can lead to unhealthy MDC nodes status.
CON-10791 USUI – Portswigger scan flags /about/api RESPONSE for sensitive version and OS info
CON-10804 USUI - Nodes - Health status is changed incorrectly from times to times for metadata controller nodes
CON-10902 Linking an existing mystornext portal account to the UUI during user-register fails due to CORS policy
CON-10988 USUI - Support of large integer value(Petabytes) in license report generated and downloaded from the UUI
CON-11015 email test fails if "Use Authentication" is enabled
CON-11051 Unified Connector Installation Challenges on Windows
CON-11082 USUI-UC On newer MacOS can fail to get the hostname if TCPv4/v6 dual stack is active
CON-11168 Enhancement request - UUI - display details about the required password complexity
CON-11172 Health status of H-Series nodes become 'indeterminate' multiple times each day.