What's New in StorNext 7.2.5

Purpose of this Release

StorNext 7.2.5 adds support for SMB Multichannel, LTO-10, and new client operating systems. This release also includes critical software fixes listed in the section Fixed Issues and Enhancements Addressed in StorNext 7.2.5.

Note: Once you upgrade StorNext software, downgrading or rolling back to a previous version is not supported.

New Features and Enhancements

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

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 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 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 StorNext appliance based clients as a part of the StorNext software upgrade process. This step does not occur for StorNext software (which includes customer-supplied hardware installations).

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 FlexSync Support

StorNext 7.2.5 only supports FlexSync 3.1.0 (or later). If you want to install StorNext 7.2.5 on your system, or upgrade your system to StorNext 7.2.5 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 node, the target node, and the managing appliance.

Caution: Mixed versions of FlexSync daemons are 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 the hosts or systems using FlexSync. A newer version of the FlexSync daemon cannot communicate with an older version within a configuration.

Compatibility and Support

The StorNext 7.2.5 Compatibility Guide provides the basic compatibility for StorNext 7.2.5, 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 compatibility guide.

Fixed Issues and Enhancements Addressed in StorNext 7.2.5

Ticket Number Description
SNXT-200 Fixes a problem where CVFS clients could see confusing I/O error messages after data offload, so file access remains reliable and understandable for admins and users.
SNXT-383

Corrects a reporting issue where files deleted during a store operation still appeared active, so file status and lifecycle information are accurate.
SNXT-465 Ensures vault operations verify that required libraries exist and are online, reducing failed jobs and making archive operations more reliable.
SNXT-812 Prevents the cvcp copy command from crashing when given invalid thread settings, so scripted and bulk copy jobs fail safely with clear behavior instead of core dumps.
SNXT-1326 Fixed a misleading error message in cvadmin related to the shared file system and mdarchives directory to be more specific, distinguishing between the shared file system not being mounted and the mdarchives directory missing.
SNXT-1478 Fixed an issue where unprivileged users are not allowed to log in during the upgrade process until the platform upgrade to StorNext 7.2.0 completes.
SNXT-1491 Fixed an issue where environments that include an Xcellis Workflow Extender that originally had StorNext version 6.1.1 or earlier installed, the upgrade will fail.
SNXT-1495 Fixed an issue where environments with a large number of LUNs visible on the Xcellis node, the node might run out of memory after the upgrade to StorNext 7.2.0.
SNXT-1530 Improves diagnostics when the REST configuration file is misconfigured, so fsmpm startup failures clearly point to the root cause and are quicker to fix.
SNXT-1536 Fixed an issue where the upgrade to StorNext 7.2.0 might fail in some cases due to a lack of free space available in the /var file system to complete the operating system conversion portion of the upgrade.
SNXT-1738 Fixed an issue where upgrades on systems originating from StorNext version 6.0.6 or earlier might fail in the pre-upgrade check when upgrading to StorNext version 7.2.0 due to the presence the obsolete rpms openssl098e and tg3 being installed.
SNXT-1773 Fixes an upgrade scenario where a service being enabled too early could break upgrades to StorNext version 7.2.x, making upgrades more predictable and resilient.
SNXT-1814 Fixed an issue by improving how the file system handles and cleans up large sets of extended attributes during file deletion, preventing an OpHang timeout and associated panic.
SNXT-1848

Add option to disable the Recycle Bin (for Windows) and the Trash (for macOS).
SNXT-1880 Updated the byte‑range lock and reconnect logic so that blocked lock requests are managed safely across client reconnects, preventing lock structure corruption and eliminating these filesystem and gateway panic conditions.
SNXT-1957 Resolves a crash when using the web console on RHEL 8 with StorNext version 7.2.0, so customers can run xdi operations through the UI without unexpected failures.
SNXT-1977 Fixes a crash in the Java-based management path, improving stability for management connections and reducing unexpected service interruptions.
SNXT-2013

Recursive or batch snretrieve/fsretrieve operations now complete successfully by default when all requested files are already on disk, and an optional system parameter is available for administrators who prefer to keep the previous no work done = error behavior.
SNXT-2019

Improved how long‑running defragmentation or file system pooling operations are monitored so they no longer get incorrectly treated as a hang, preventing these unnecessary panics and improving overall system stability during heavy defragmentation or file system pooling workloads.
SNXT-2046

Adds an option to accept the StorNext client EULA silently, enabling fully automated and scripted client deployments without manual prompts.
SNXT-2066 Improves how StorNext handles archived data so retrieves for expired Glacier objects fail more predictably and are easier for admins to understand and manage.
SNXT-2068 Enhances fsqueue -f output so it includes file names and paths for truncated files, giving better visibility for troubleshooting and audits.
SNXT-2078 This release updates the interaction between snaccess and the purge logic so that restricted directories no longer trigger these excessive kernel spins, preventing the soft lockups and improving overall stability for Linux clients using snaccess access controls.
SNXT-2080 Updates lifecycle and end-of-life decisions to rely on current, supported metrics instead of deprecated LP3 counts, so retention and migration behavior better matches expectations.
SNXT-2099 Fixes allocation issues so large files can still be placed efficiently even when free space is highly fragmented, improving capacity usage and reducing allocation failures.
SNXT-2102 Improve the upgrade reliability for systems that were originally installed on older releases and still have legacy or “dangling” Docker images; the upgrade process has been updated so these untagged images are handled correctly, allowing the overlay-to-overlay2 conversion to complete and preventing upgrade failures on systems with old or dangling Docker images.
SNXT-2123 Prevents client crashes when the same metadata controller is configured with multiple IP addresses, improving stability in multi-path and multi-network setups.
SNXT-2157 Resolves failures in samfsimport on Rocky Linux 7.2.x, allowing customers to import data successfully on that platform.
SNXT-2169 Fixes an issue so that StorNext now correctly recognizes this combined power‑supply status and raises the appropriate FRU/RAS events and UI alerts whenever a power supply loses AC power or is removed, ensuring that hardware issues are clearly reported to administrators.
SNXT-2211 Fixes a low-level memory error that could cause crashes when opening files, improving overall system stability under load.
SNXT-2240 Corrects a condition where file system pooling could loop on certain zero-length files and consume excessive CPU, improving performance and reducing unnecessary resource usage.
SNXT-2271 Fixed an issue where Xcellis systems running StorNext version 7.2.x systems on Rocky Linux (OS8) did not include the required postfix package that provides /usr/sbin/sendmail. This prevented mailx from sending email notifications (including sntierd email delivery). The postfix RPM is now installed on both fresh and upgraded Xcellis systems running StorNext version 7.2.5 or later, restoring expected email functionality.