The StorNext 6.1 release delivers support for a pair of new non-expiring FlexTier licenses, plus software fixes that correct the Spectre and Meltdown security vulnerabilities (variants) listed in the tables below.
|StorNext Release||Operating System||Kernel||Variant Addressed|
|22.214.171.124||Red Hat EL / CentOS 6 Update 9||2.6.32-696.30.1||1,2,3,4|
|Red Hat EL / CentOS 7 Update 4||3.10.0-693.21.1||1,2,3|
|6.1.0||Red Hat EL / CentOS 6 Update 9||2.6.32-696.30.1||1,2,3,4|
|Red Hat EL / CentOS 7 Update 5||3.10.0-862.11.6|
Note: Software-only configurations must get BIOS fixes from their hardware vendor.
Caution: StorNext 126.96.36.199 does not work when used with Red Hat EL / CentOS 7 update 5. If you are an administrator of a non-StorNext Appliance system, then you must be careful when upgrading a Red Hat EL / CentOS operating system. You must only upgrade to levels supported in the StorNext 6 Compatibility Guide.
Quantum Appliance Configuration
Spectre and Meltdown vulnerabilities are not addressed in StorNext 188.8.131.52.
Red Hat/CentOS 6 Update 9
Red Hat/CentOS 7 Update 4
The duplicate a file copy feature provides the capability to store another copy of a file. This feature is useful when the default copies for a policy class are increased and the desire is for existing files in the policy to take on the new setting. You can use the fsfilecopy command to invoke this capability.
The new -n option indicates the new copy to create. The specified new copy cannot exceed the policy class max copies setting. It is only allowed to be one larger than the current default copies setting for each file being processed. For example, if a file has default copies of 2, then the new copy value can be no larger than 3, so copies are not skipped.
For the new copy operation, logic was added when processing error conditions for a file to determine if they are fatal or if the command should continue processing. Most conditions were considered to be non-fatal. A summary of these conditions with the number of files falling into each category is displayed just before the processing begins to make the new copy of truncated files.
Below is a sample of the summary:
FS0355 04 0009486129 fsfilecopy interim: File scan summary
FS0355 04 0009486129 fsfilecopy interim: 4 files already store candidates.
FS0355 04 0009486129 fsfilecopy interim: 3 files the copy already exists.
FS0355 04 0009486129 fsfilecopy interim: 1 file belonged to another class.
FS0355 04 0009486129 fsfilecopy interim: 1 file had no content.
FS0355 04 0009486129 fsfilecopy interim: 1 file is a directory.
FS0355 04 0009486129 fsfilecopy interim: 2 files didn't exist.
FS0355 04 0009486129 fsfilecopy interim: 1 file not in archival directory.
FS0355 04 0009486129 fsfilecopy interim: 1 file exceeded max path length.
FS0355 04 0009486129 fsfilecopy interim: 100 files will be copied.
The new limit (-L) option allows you to throttle the request by limiting the number of I/O requests that are generated.
Note: The default limit of I/O requests you can generate is 10. For requests using tape devices, this is the number of queued I/O requests. Tape I/O requests are processed sequentially, so there is no benefit in adjusting this value. Quantum recommends you use the default setting.
For requests that do not involve tape devices, limiting the number of I/O requests also restricts the number of streams that you use. The number of streams that you can use is the lesser of the limit value or the max streams defined for the device. The stream limit is applied to each source and destination device so the specified limit value is used for each. For example, if you specify -L 3, then 6 streams are used; 3 streams are used for the source and 3 streams are used for the destination.
However, if you define the max streams for one of the devices to be smaller, then the request is further restricted. Using the same example, if you configured the source device with max streams of 2, then only up to 2 streams are used for each source and destination devices.
Note: When you set this value for non-tape devices, keep in mind that fsfilecopy(1) requests run at a lower priority than store and retrieve requests, so the requests only use available streams when there are no outstanding store/retrieve requests requiring those resources.
Note: Prior to StorNext 6.1, you could only allow a list of files to be specified. Beginning with StorNext 6.1, you can include options to operate recursively on a directory or on a batch file containing a list of files.
For additional information, refer to the fsfilecopy(1) command in the StorNext 6 Man Pages Reference Guide.
The StorNext 6 Compatibility Guide provides the basic compatibility for StorNext 6.1, includes 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 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.
|Operating System||Change Request Number||
Service Request Number
|All||65301||293344, 332924||cvmkfs hangs if DNS is not reachable|
|All||66283||3748382, 414432||Proxy Client cvfsbufiod spinning in PickPxcon() after adding stripe groups|
|All||62209||3636874, 414352, 429898||security scan - Autocomplete Not Disabled|
|All||71237||3584660||provide capability to make a new copy from an existing copy|
|All||72070||439940||Retrieves from a 100% full non-tape media fail|
|All||71908||435562 429352, 440980||fs_copymand core caused by fsqueue query due to timing issue dumping the queue as it is cleared|
|All||71534||423796||xdiamtask core due to unknown check condition|
|All||71493||423302, 443878, 444771, 445912||QRDB corruption at 2 billion object IDs due to int32 overflow|
|All||71491||422731||unresolvable hostname in nss_cctl.xml control file permitted retrieves on clients although denyRetrieves value = true|
|All||71413||419495, 445375||GUI:File and Directory Actions - Retrieve Directory not working|
|All||71296||417960, 346928, 411188||Multiple OpHangLimitSec panics|
|All||71061||4020160 ,427408||Upgrade issues resulted in removal of TSM libmsc.so library and problems starting TSM fs_resourced daemon|
|All||71243||416889, 416858, 423186, 426962||fs_resourced segfault occurred upon fsmedin, leading to TSM abnormal termination|
|All||71212||414396||SNFS: snaudit shows wrong host IP on some rm actions|
|All||71240||408782||fsimport will not import files with some special characters in them|
|All||71102||407649, 403677||snbackup failed with "ERR: Failed to store copy" even though the copy was successful|
|All||61553||384152||fs_resourced can core and halt TSM when fsmedcopy is run|
|All||71179||380802, 362953||FSM panics for file names with non-ASCII characters|
|All||70294||378110||snaudit may use all available memory of system on busy system until the kernel kills it|
|All||70224||376518||fs_moverd: not accessible/working due to bad /etc/hosts value|
|All||68141||344165||vidio tools for the Mac|
|All||67827||415475||in the fsm, whenever using a pclient structure, we should make sure it is valid ...|
|All||71291||n/a||Update fsfileinfo v2 web service call to support object url, encryption and compression information|
|Linux||71230||414352, 429898||Security scan reports HTTP Header missing on port 443|
|Linux||71229||414352, 349865||Security scanner showed StorNext GUI allowed connection on TLSv1.2 with DES cipher|
|Windows||70846||433642||StorNext Gateway Server may cause a system hang on Windows systems|