What's New in StorNext 6.4.1
Purpose of this Release
The StorNext 6.4.1 release provides software fixes listed in the section Fixed Issues and Enhancements Addressed in StorNext 6.4.1.
New Features and Enhancements in StorNext 6.4.1
Support for Operating Systems
Beginning with StorNext 6.4.1, the following operating systems are supported:
- Red Hat Enterprise Linux (RHEL) 7 Update 8
- Red Hat Enterprise Linux (RHEL) 7 Update 9
- Red Hat Enterprise Linux (RHEL) 8 Base
- Red Hat Enterprise Linux (RHEL) 8 Update 1
- CentOS 7 Update 8
- CentOS 7 Update 9
- CentOS 8 Base
- CentOS 8 Update 1
For complete details, see the StorNext 6.4.1 Compatibility Guide.
Information About StorNext Upgrades

Due to the potential of the MySQL database corruption when you upgrade the release of the MySQL database, Quantum added logic to the upgrade utilities to ensure that the MySQL database is cleanly shut down on upgrade (reference StorNext Bugzilla Bug 77325).
The database is shut down using a "slow shutdown" process in a MySQL setting; the setting used for the database shut down is documented in the MySQL Reference Manual (see InnoDB shutdown mode).
There are instances where excessive slowdowns on upgrade occur due to the "slow shutdown" of the MySQL database (reference StorNext Bugzilla Bug 78960).

Quantum assessed the "slow shutdown" process is ONLY required when you upgrade from a major release of MySQL to another major release.
Note: A major release of MySQL is signified by a change to the second digit in the release number. For example, MySQL 5.6 to MySQL 5.7.
The table below provides the MySQL release included in each StorNext release.
StorNext Release |
MySQL Release |
---|---|
5.1.1 through 6.1.1 |
5.6 |
6.2.0 through 7.0.1 |
5.7 |
Quantum recommends the following, according to the releases in the table above:
-
If you are upgrading from StorNext 6.2.0 through StorNext 7.0.1, then you are NOT required to perform the "slow shutdown" process.
-
If you are upgrading from StorNext 6.1.1 (or earlier) to StorNext 6.2.0 (and later), then you MUST perform the "slow shutdown" process to avoid potential database corruption.

The following section describes the remedy for customers doing an upgrade.

Before you initiate a StorNext upgrade, add a line of text to the /usr/adic/mysql/bin/mysql_control script on both the primary and secondary MDCs to enable a fast shutdown immediately before the command to shutdown MySQL (and avoid the slow shutdown).
For example, the highlighted text in the code snippet below illustrates the line to add in the mysql_control script:
stop)
stopit=0
if mysqld_running
then
stopit=1
if [ -f $ENABLE_CLEAN_SHUTDOWN ] ; then <- Not present in earlier releases
log_out "Requesting clean database shutdown" <- Not present in earlier releases
$MYSQL_DIR/bin/mysql -e "set global innodb_fast_shutdown=0" <- Not present in earlier releases
fi <- Not present in earlier releases
log_out "Stopping mysqld"
$MYSQL_DIR/bin/mysql -e "set global innodb_fast_shutdown=1"
$MYSQL_DIR/bin/mysqladmin --defaults-file=$MY_CNF shutdown
sleep 1
fi
After you add the line of text to the mysql_control script, then you can initiate the upgrade process.
Note: Do not be concerned about backing out the script change after the upgrade is finished; the StorNext upgrade process overwrites the mysql_control script.

Quantum recommends you perform a "slow shutdown", as the upgrade is currently doing. The upgrade process might require additional time due to the clean shutdown of the database during the upgrade.
Note: It is not possible to estimate the amount of time required for the upgrade process.

To prevent manual intervention in the upgrade process, Quantum plans to add logic to the StorNext upgrade process, that verifies the MySQL version (reference StorNext Bugzilla Bug 79053).
Compatibility and Support
The StorNext 6.4.1 Compatibility Guide provides the basic compatibility for StorNext 6.4.1, 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 6.4.1 Compatibility Guide.
- Upgrade Paths: Provides information on what upgrades to this release are supported.
- Appliance Support: Provides information on what StorNext and Lattus appliances are supported with this release or are compatible with it.
- Operating Systems and Platforms: Provides information on what StorNext components run on various operating systems and service packs. Also includes which operating systems have been newly added or removed.
- Client Interoperability: Provides information on what StorNext clients running other versions of StorNext are compatible with metadata-controllers (MDCs) running this release.
- Virtual Machine Support: Provides information on what StorNext components running on selected operating systems and service packs are supported in virtual machines.
- Compatibility with Other Products: Provides information on references to additional StorNext sold-separately products that are supported with this release.
- Browser Support: Provides information on what versions of browsers are supported with the GUI in this release.
- Drives and Libraries: Provides information on what Quantum and 3rd party drives and libraries are supported with this release.
Fixed Issues and Enhancements Addressed in StorNext 6.4.1
Operating System | Change Request Number |
Service Request Number |
Description |
---|---|---|---|
All | 73496 | 465444, 577160 | ArcDisp hit OOM condition and got killed, leading to MSM abnormal termination |
All | 75143 | 525455 | ENOENT returned for lookups on linux 7.6 with storage manager |
All | 75213 | 526974, 555991, 566835, 570951, 570482 | Misleading message on MDC w.r.t san_client DOWN disk devices |
All | 75468 | 512218, 569557 | fsimport fails to import media with the hardware write lock set |
All | 76615 | 560280 | Auditing generates a nodechange to every client on a close |
All | 76970 | 546119, 554609, 576026,578397, 576097, 571413, 597177 | fsm panic upon ASSERT failed "pclient->cl_rsvd_counted == 0" |
All | 76997 | 543055, 571150, 576036, 576037, 577537, 569740, 578514,578812, 580923, 578146, 586085, 585472, 592724, 599629 | Long running transaction in UI logic - this MAY result in growing ibdata1 file |
All | 77221 | 553837, 580930 | wsar_agent is running into heap exhaustion due to MariaDB mem_root implementation |
All | 77283 | 555650 | GUI: modify policy "Copy Expiration" warning to be more explicit about file deletion |
All | 77481 | 589728 | find command return IO error when running prodcon |
All | 77515 | 560062 549992 | FSM: PANIC: /usr/cvfs/bin/fsm ASSERT failed "IP_IS_SPACE_TREE(ip) || this.idiext_frblock + extsize <= next.idiext_frblock" |
All | 77547 | 549992 | FSM: PANIC: /usr/cvfs/bin/fsm ASSERT failed "IP_IS_SPACE_TREE(ip) || this.idiext_frblock + extsize <= next.idiext_frblock" |
All | 77646 | 559566, 570899 | ls of a directory failing on a clientwith "Input/output error" while mdc is creating many files in it. |
All | 77653 | 563234, 563898 | Mysqld fails to start after upgrading to StorNext version 6.4.0 |
All | 77678 | 563234, 563898 | file-per-table conversion needs to account for sys_config.ibd file |
All | 77730 | 564850 | Snapshot: Include contents of files in the /usr/adic/TSM/internal/locks directory |
All | 77746 | n/a | Red Hat (RHEL) 7 update 8 Client Support |
All | 77771 | 567119 | Reduce the processing time of request api files_by_media with small number of truncated files |
All | 77812 | n/a | GUI: Red Hat (RHEL) 7 update 8 Client Support |
All | 77861 | 569557 | The fsmedscan util is producing extraneous fields that causes fsimport to fail |
All | 77879 | 561495 | Disks and Path of mulitpath devices set to standby |
All | 77944 | 587504 | Google multi-part upload fails with bad request error |
All | 78022 | 563167 | RPM script change needed to mod inotify max_user_watches to 32768 in sysctl.conf |
All | 78031 | 574044, 581478, 578897 | fs_moverd segmentation fault occurs on multipart upload to Google Cloud Storage, with full payload disabled |
All | 78051 | 577213 | install.stornext will not upgrade components if previous install did not fully complete |
All | 78105 | 579144 | snrecover process deadlocks restoring files that have been deleted |
All | 78116 | 578751, 583673 | fsretrieve -R fails if the files are stored on SAMFS tapes |
All | 78146 | 580579 | fs_moverd segmentation fault occurs during Google delete batch request, due to null-string boundary |
All | 78188 | 581921, 589950 | fs_resourced crashing frequently after reporting many "No controllers found" errors |
All | 78292 | 583924 | fsimport can fail to import tapes if a directory has a single quote in the name |
All | 78315 | 585257 | fsrecover is unable to recover files from a long directory path |
All | 78508 | 591254 | Google objects left orphaned after parallel upload errors |
All | 78518 | n/a | Update quantum_disk_catalog to include F-Series and H-Series entries for Quantum Branded disk. |
All | 78520 | 588842 | CVFS down_write()'s i_rwsem without holding the semaphore |
All | 78523 | n/a | When Windows DLC clients run continuous I/O to a file system that has been remade and resized, mdc kernel panics upon mounting the new FS |
All | 78601 | 591208 | Windows Explorer large file copy takes several seconds to report any progress when buffer cache >= 4GB |
Linux | 74545 | 501127, 493912, 501127 | Ubuntu Kernel 4.4.0.145 new get_user_pages() signature, cvfsbuild fails error: too many arguments to function 'get_user_pages' |
Linux | 77804 | n/a | 6.4.x Client Support for CentOS/RHEL 8 |
Linux | 77932 | n/a | GUI: 6.4.x Client Support for CentOS/RHEL 8 |
Linux | 77934 | n/a | Include CentOS/RHEL 8 Client package in 6.4.1 |
Linux | 78070 | 577099 | Ubuntu: mounting an Image as loopback result in "mount: /dev/loop0: can't read superblock" |