You must have a licensed version of IBM Spectrum Scale 4.2.2 or higher installed.

After you have downloaded the IBM Spectrum Scale 4.2.2.1 update, follow the steps below to install the fix package:

Ensure the package is executable using ls -l command.

You should see something similar with permissions like:
-rwxr--r-- l root root 110885866 Apr 27 15:52 /download_dir/package_name.

If it's not executable, you can always make the package executable using the following command:
chmod +x /download_dir/package_name
Extract RPMs from Self Extracting Package downloaded using following commands:

For Express Edition:
./Spectrum_Scale_Express-4.2.2.1-s390x-Linux-install

For Standard Edition:
./Spectrum_Scale_Standard-4.2.2.1-s390x-Linux-install

For Advanced Edition or Data Management Edition:
./Spectrum_Scale_Advanced-4.2.2.1-s390x-Linux-install

By default, the RPMs will be extracted to the following location: /usr/lpp/mmfs/4.2.2.1

Required packages (SLES and RHEL Linux):
- gpfs.base-4.2.2.1.s390x.rpm
- gpfs.gpl-4.2.2.1.noarch.rpm
- gpfs.msg.en_US-4.2.2.1.noarch.rpm
- gpfs.docs-4.2.2.1.noarch.rpm
- gpfs.ext-4.2.2.1.s390x.rpm (IBM Spectrum Scale Standard and Advanced Edition or IBM Spectrum Scale Data Management Edition only)
- gpfs.adv-4.2.2.1.s390x.rpm (IBM Spectrum Scale Advanced Edition or IBM Spectrum Scale Data Management Edition only)
- gpfs.gskit-8.0.50-47.s390x.rpm
- gpfs.license.xxx-4.2.2.1.s390x.rpm (where xxx is the license type)
Follow the installation and migration instructions in your IBM Spectrum Scale Concepts, Planning and Installation Guide.

Upgrading GPFS may be accomplished by either upgrading one node in the cluster at a time or by upgrading all nodes in the cluster at once. When upgrading GPFS one node at a time, the below steps are performed on each node in the cluster in a sequential manner. When upgrading the entire cluster at once, GPFS must be shutdown on all nodes in the cluster prior to upgrading.

When upgrading nodes one at a time, you may need to plan the order of nodes to upgrade. Verify that stopping each particular machine does not cause quorum to be lost or that an NSD server might be the last server for some disks. Upgrade the quorum and manager nodes first. When upgrading the quorum nodes, upgrade the cluster manager last to avoid unnecessary cluster failover and election of new cluster managers.

Prior to upgrading GPFS on a node, all applications that depend on GPFS (e.g. DB2) must be stopped. Any GPFS file systems that are NFS exported must be unexported prior to unmounting GPFS file systems.
Stop GPFS on the node. Verify that the GPFS daemon has terminated and that the kernel extensions have been unloaded (mmfsenv -u). If the command mmfsenv -u reports that it cannot unload the kernel extensions because they are "busy", then the install can proceed, but the node must be rebooted after the install. By "busy" this means that some process has a "current directory" in some GPFS filesystem directory or has an open file descriptor. The freeware program lsof can identify the process and the process can then be killed. Retry mmfsenv -u and if that succeeds then a reboot of the node can be avoided.
Upgrade GPFS using the RPM command as follows(make sure to be in the same directory as the files):

For SLES or RHEL systems:
rpm -Fvh gpfs*.rpm
Install license file(make sure to be in the same directory as the files):

rpm -ivh gpfs.license.*.rpm
Recompile any GPFS portability layer modules you may have previously compiled. For more information, reference: Building the GPFS portability layer on Linux nodes

The update images listed below and contained in the Self Extracting Package (SE-Package) are maintenance packages for IBM Spectrum Scale. The update images are a mix of normal RPM images that can be directly applied to your system.

The update images require a prior level of IBM Spectrum Scale. Thus, the usefulness of this update is limited to installations that already have the IBM Spectrum Scale product. Contact your IBM representative if you desire to purchase a fully installable product that does not require a prior level of IBM Spectrum Scale.

After all RPMs are installed, you have successfully updated your IBM Spectrum Scale product.

Before installing IBM Spectrum Scale, it is necessary to verify that you have the correct levels of the prerequisite software installed on each node in the cluster. If the correct level of prerequisite software is not installed, see the appropriate installation manual before proceeding with your IBM Spectrum Scale installation.

For the most up-to-date list of prerequisite software, see the IBM Spectrum Scale FAQ in the IBM® Knowledge Center .

Update to Version:

4.2.2.1

Update from Version:

4.2.0.0-4.2.0.3

Update (SE-Package) contents (SLES and RHEL):

gpfs.base.4.2.2.1.s390x.rpm
gpfs.docs.4.2.2.1.noarch.rpm
gpfs.gpl.4.2.2.1.noarch.rpm
gpfs.gskit-8.0.50-47.s390x.rpm
gpfs.msg.en_US.4.2.2.1.noarch.rpm
gpfs.ext.4.2.2.1.s390x.rpm (IBM Spectrum Scale Standard and Advanced Editions only)
gpfs.adv.4.2.2.1.s390x.rpm (IBM Spectrum Scale Advanced Edition only)
gpfs.license.xxx-4.2.2.1.s390x.rpm (where xxx is the license type)

Unless specifically noted otherwise, this history of problems fixed for IBM Spectrum Scale 4.2.x applies for all supported platforms.

Problems fixed in IBM Spectrum Scale 4.2.2.1 [December 16, 2016]

CNFS: fix recursive calls during shutdown which may cause LOGASSERT.
Fix data corruption that can occur writing large files using parallel IO and multiple gateway nodes.
Fix a kernel crash during mmshutdown in kxAttachSharedMemory by tsctl process.
Fix "mutexMagic != 0x59C0DEAD" assert by the SGExceptionLocalPanicThread that can occur during quorum loss.
mmlsfileset: allow remote file system. Option -i and -d are now allow.
mmstartup: verify kernel/module configuration before start runmmfs.
Fix a very rare race condition that can lead to kernel panic. This issue could only occur on Linux when a mix of AIO and buffered IO are being used to read and write to the same file from multiple nodes.
Fix data mismatch problems and snapshot mismatches between old primary and acting primary during an applyUpdates in the failbackToPrimary procedure.
Fix a problem in which mmbackup returns the wrong number of objects handled. This can occur if NUMBERFORMAT is set incorrectly.
Fix Kernel BUG: illegal operation locks_wake_up_blocks+0x6c.
mmlsconfig: may not return correct value due to stale cache.
Fix code to prevent a possible kernel panic during GPFS daemon shutdown on Linux. In order for problem to occur, filesystem must be mounted with active workload when GPFS daemon is been shutdown.* Fix assert in the Gpfs daemon by disallowing GetAttr for DR Primary fileset.
Fix assert in the daemon that can occur during a Gateway queue transfer and new gateway node joins at the same time.
Fix slow offline fsck repair. Allow doDeferredDeletions() to cleanup afm pre-destroyed inodes in ex-afm filesets.
Fix a deadlock that can occur if a node of the cluster is down while GPFS attempts to establish a RDMA connection using RDMA CM.
Fix an issue in AFM environment where queue memory usage threshold (afmHardMemThreshold) is not honored.
Fix a remote error 17 creating and deleting hardlinks to files during log recovery.
Fix a mmsdrrestore command failure that can occur when a tiebreaker disk is in use (CCR setup).
This fix will make sure data is synced to disk only when required.
Fix mmfsd crash in an AFM environment that can occur when a lookup on the same file is triggered from multiple nodes.
Fix a debug assert in performPcacheMsg that can occur when the hardQMemLimit is hit for a fileset.
During IFS System upgrade, occasionally node crash is observed if AFM is configured and in use.
Fix Renames clogging the AFM queue during recovery for IW filesets.
Apply this fix if you are troubled by bogus messages in the mmfs log files during file system creation.
This modification does not change the functionality of GPFS, neither affects the appearance of the software, however it improves the effectiveness (speed) of the code in certain disk operations and introduces a mechanism (by explicitly distinguishing user- and kernel-space objects) that can be used for implementing other critical parts on s390x platform.
Fix a deadlock that can occur during high volume file creations and deletions in a multi cluster environment.
Fix mmlsquota -j returning a wrong answer that can occur if there is a special character in the name of the stripe group.
Handle upgrade of Windows node from 3.5 and 4.1 to 4.2 correctly.
Fix a problem in which mmces fails to change the address of object protocol attributes.
Honor parent folder's DELETE_CHILD right during rename operation from Windows node.
Fix a problem in which mmbackup with -B value > 32768 causes missed files.
Applications using dmapi for HSM may benefit by knowing if a file that is being migrated is currently open and being accessed on some node in the cluster. Extend the dmapi dm_get_fileattr command to take a new flag "DM_AT_FOPEN" to query if the file is open anywhere in the cluster.
Prevent the execution of mmhealth on unsupported nodes.
Change in dmapi dm_stat_t structure returned by dm_get_fileattr used by TCT. Update must be coordinated with TCT update.
This update addresses the following APARs: IV90831 IV90833 IV90864 IV90865 IV90869 IV90874 IV90878 IV90880 IV90891 IV90892 IV91054 IV91144 IV91145 IV91327 IV91443.

Copyright and trademark information

http://www.ibm.com/legal/copytrade.shtml

Notices

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Microsoft, Windows, and Windows Server are trademarks of Microsoft Corporation in the United States, other countries, or both.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Other company, product, or service names may be trademarks or service marks of others.

THIRD-PARTY LICENSE TERMS AND CONDITIONS, NOTICES AND INFORMATION

The license agreement for this product refers you to this file for details concerning terms and conditions applicable to third party software code included in this product, and for certain notices and other information IBM must provide to you under its license to certain software code. The relevant terms and conditions, notices and other information are provided or referenced below. Please note that any non-English version of the licenses below is unofficial and is provided to you for your convenience only. The English version of the licenses below, provided as part of the English version of this file, is the official version.

Notwithstanding the terms and conditions of any other agreement you may have with IBM or any of its related or affiliated entities (collectively "IBM"), the third party software code identified below are "Excluded Components" and are subject to the following terms and conditions:

the Excluded Components are provided on an "AS IS" basis
IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
IBM will not be liable to you or indemnify you for any claims related to the Excluded Components
IBM will not be liable for any direct, indirect, incidental, special, exemplary, punitive or consequential damages with respect to the Excluded Components.

Product/Component Name:	Platform:	Fix:
IBM Spectrum Scale	Linux390 64-bit RHEL Linux390 64-bit SLES	Spectrum_Scale_Advanced-4.2.2.1-s390x-Linux

Readme and Release notes for release 4.2.2.1 IBM Spectrum Scale 4.2.2.1 Spectrum_Scale_Advanced-4.2.2.1-s390x-Linux Readme