You may use this 4.2.3.2 package to perform a First Time Install or to upgrade from an existing 4.1.0.0 - 4.2.3.1 (If upgrading node by node ) or 3.5.0 - 4.2.3.1 (If you shutdown and upgrade the entire cluster).

After you have downloaded the IBM Spectrum Scale 4.2.3.2 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 packages from the Self Extracting Package downloaded using following commands:

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

For Advanced Edition:
./Spectrum_Scale_Advanced-4.2.3.2-s390x-Linux-install

For Data Management Edition:
./Spectrum_Scale_Data_Management-4.2.3.2-s390x-Linux-install

By default, the RPMs and Debian Linux packages will be extracted to the following location: /usr/lpp/mmfs/4.2.3.2

Required packages (SLES and RHEL Linux):
- gpfs.base-4.2.3-2.s390x.rpm
- gpfs.gpl-4.2.3-2.noarch.rpm
- gpfs.msg.en_US-4.2.3-2.noarch.rpm
- gpfs.docs-4.2.3-2.noarch.rpm
- gpfs.ext-4.2.3-2.s390x.rpm
- gpfs.gskit-8.0.50-75.s390x.rpm
- gpfs.gui-4.2.3-2.noarch.rpm
- gpfs.java-4.2.3-2.s390x.rpm
- gpfs.license.xxx-4.2.3-2.s390x.rpm (where xxx is the license type)
- gpfs.crypto-4.2.3-2.s390x.rpm (IBM Spectrum Scale Advanced Edition or IBM Spectrum Scale Data Management Edition only)
- gpfs.adv-4.2.3-2.s390x.rpm (IBM Spectrum Scale Advanced Edition or IBM Spectrum Scale Data Management Edition only)
- gpfs.gss.pmcollector-4.2.3-2.xxx.s390x.rpm (where xxx is the OS version)
- gpfs.gss.pmsensors-4.2.3-2.xxx.s390x.rpm (where xxx is the OS version)
Required packages (Debian Linux):
- gpfs.msg.en_us-4.2.3-2_all.deb
- gpfs.base-4.2.3-2_s390x.deb
- gpfs.crypto_4.2.3-2_s390x.deb
- gpfs.gpl-4.2.3-2_all.deb
- gpfs.docs-4.2.3-2_all.deb
- gpfs.ext-4.2.3-2_s390x.deb
- gpfs.gskit_8.0.50-75.s390x.deb
- gpfs.gui-4.2.3-2_all.deb
- gpfs.java-4.2.3-2_390x.deb
- gpfs.gss.pmcollector_4.2.3-2.U16.04_s390x.deb
- gpfs.gss.pmsensors_4.2.3-2.U16.04_s390x.deb
- gpfs.license.xxx_4.2.3-2_s390x.deb (where xxx is the license type)
- gpfs.adv_4.2.3-2_s390x.deb (IBM Spectrum Scale Advanced Edition or IBM Spect rum Scale Data Management Edition only)
Follow the installation and migration instructions in your IBM Spectrum Scale Installing and upgrading.

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 as follows(make sure to be in the same directory as the files):

For SLES or RHEL systems:
rpm -Fvh gpfs*.rpm rpm -ivh gpfs.license.*.rpm (if you are updating from 4.2.1.2 or older versions)

For Debian systems:
dpkg -i gpfs*.deb
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 or Deb 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 or Debs 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.3.2

Update from Version:

4.1.0.0 - 4.2.3.1 (If upgrading node by node )
3.5.0 - 4.2.3.0 (If you shutdown and upgrade the entire cluster)

Installing IBM Spectrum Scale update for Linux on System z
After you have downloaded the IBM Spectrum Scale 4.2.3.2 update, follow the steps below to install the fix package:
1. 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
2. Extract RPMs from Self Extracting Package downloaded using following commands:
  
  For Standard Edition:
  ./Spectrum_Scale_Standard-4.2.3.2-s390x-Linux-install
  
  For Advanced Edition:
  ./Spectrum_Scale_Advanced-4.2.3.2-s390x-Linux-install
  
  For Data Management Edition:
  ./Spectrum_Scale_Data_Management-4.2.3.2-s390x-Linux-install
  
  By default, the RPMs will be extracted to the following location: /usr/lpp/mmfs/4.2.3.2
  
  Update (SE-Package) All Editions contents (SLES and RHEL):
  - gpfs.base-4.2.3-2.s390x.rpm
  - gpfs.gpl-4.2.3-2.noarch.rpm
  - gpfs.msg.en_US-4.2.3-2.noarch.rpm
  - gpfs.docs-4.2.3-2.noarch.rpm
  - gpfs.ext-4.2.3-2.s390x.rpm
  - gpfs.gskit-8.0.50-75.s390x.rpm
  - gpfs.gui-4.2.3-2.noarch.rpm
  - gpfs.java-4.2.3-2.s390x.rpm
  - gpfs.license.xxx-4.2.3-2.s390x.rpm (where xxx is the license type)
  - gpfs.crypto-4.2.3-2.s390x.rpm (IBM Spectrum Scale Advanced Edition or IBM Spectrum Scale Data Management Edition only)
  - gpfs.adv-4.2.3-2.s390x.rpm (IBM Spectrum Scale Advanced Edition or IBM Spectrum Scale Data Management Edition only)
  Update (SE-Package) Advanced and Data Managemen Editions contents (Debian Linux):
  - gpfs.msg.en_us-4.2.3-2_all.deb
  - gpfs.base-4.2.3-2_s390x.deb
  - gpfs.crypto_4.2.3-2_s390x.deb
  - gpfs.gpl-4.2.3-2_all.deb
  - gpfs.docs-4.2.3-2_all.deb
  - gpfs.ext-4.2.3-2_s390x.deb
  - gpfs.gskit_8.0.50-75.s390x.deb
  - gpfs.gui-4.2.3-2_all.deb
  - gpfs.java-4.2.3-2_390x.deb
  - gpfs.license.xxx_4.2.3-2_s390x.deb (where xxx is the license type)
  - gpfs.adv_4.2.3-2_s390x.deb (IBM Spectrum Scale Advanced Edition or IBM Spect rum Scale Data Management Edition only)
3. Follow the installation and migration instructions in your IBM Spectrum Scale Installing and upgrading.

Upgrading GPFS nodes
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.
1. 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.
2. 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.
3. 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 rpm -ivh gpfs.license.*.rpm (if you are updating from 4.2.1.2 or older version)
  
  For Debian systems:
  dpkg -i gpfs*.deb
4. Recompile any GPFS portability layer modules you may have previously compiled. For more information, reference: Building the GPFS portability layer on Linux nodes

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.3.2 [June 21, 2017]

Address a problem where AFM recovery stalls on a read of an IW fileset when it waits to fetch the file from home after the recovery completes.
Improve a conditional ccr update for CES IPs list file.
Fix a problem that causes RenameHandler long waiter. This can occur if PIT is in progress.
Fix a Ganesha crash that can occur when the user enters a string which contains a colon in any mmnfs command that requires a client option or client list string.
Fix an assert that can occur when changing gateway nodes to non gateway nodes while operations are being performed on an iw fileset and then the non gateway nodes are turned back into gateway nodes.
Fix a rare deadlock that can occur between a thread handling mmap and a thread handling a memory map pagefault.
Fix an E_STALE failure that can occur when during a DMAPI dm_read_invis.
Fix long waiters that can occur on a very busy system doing background snapshot deletion.
Fix a case where GPFS skipped shrinking lastdata block which causes excess space to be consumed.
Improve the mmsetquota error message that occurs when a block limit is specified in 'T' unit and larger than 909T is specified.
Fix an assert that can occur when mmcheckquota and mmrepquota are passed fileset ids from deleted filesets.
Fix an issue in the AFM environment where afmHardMemThreshold configuration value is not honored and more memory is used than specified.
Increase the wait time for commands to execute, before failing.
Correct formatting of large call counts reported by "mmfsadm vfsstats".
Fix long waiters that can occur after a file system panic and a very busy system.
Fix a problem in which inodes become Busy after unmount with NFS and immutable files.
mmkeyserv: Make it possible to set certain attributes to the default with the use of "delete" or "default" keyword.
Fix a problem in which mkdir, creates, and resync can fail during revalidation from cache/primary to home/secondary in newer kernels 3.18 or later.
Fix a problem in which GPFS can not handle errors that occur when a DM application was unable to retrieve data due to offline tape.
Suppress repeated message "Expanded ... inode space N from X to Y inodes" in mmfs.log.
Fix a rare quota management deadlock caused by error conditions such as out of disk space.
Fix an issue in AFM+HSM environment where resync/failover/changeSecondary commands fails to replicate migrated files.
Fix an issue in the AFM environment where a fileset force unlink could cause the daemon to crash.
Address a problem where a gateway node can assert/crash when having more than 1024 active fileset operations occurring across different filesets on a single gateway node.
Fix a problem in which gpfs.snap may not gather mmfs logs on AIX nodes correctly.
Fix a clone parent file deletion performance issue.
Fix a problem in which fsetxattr failed with ENOENT using a fd of an unlinked file.
Fix the Assert exp(fileLockHeld != LkObj::nl) in fetchBufferM() that can occur when compression is being used.
Fix a problem where DMAPI invis read/write fails with an err 22 when calling from non session node.
Fix a problem in which the mmnetverify command does not correctly verify remote addresses when running many tests in parallel.
Fix a deadlock that is very rare and can occur after running snapshot commands.
Fix a policy problem which causes the LOWDISKSPACE callback to not trigger after a fs manager takeover when the old fs manager fails because of an abort or a lost connection.
This update addresses the following APARs: IV96355 IV96416 IV96417 IV96418 IV96419 IV96420 IV96425 IV96426 IV96429 IV96472 IV96473 IV96474 IV96476 IV96482 IV96483 IV96487 IV96488 IV96585 IV96761 IV96762 IV96763 IV96764 IV96783 IV96786 IV96791.

Problems fixed in GPFS 4.2.3.1 [May 16, 2017]

Fix a Ganesha crash caused by an applyUpdate.
Fix a ccrio initialization failure (err 811) when changing the daemon-interface.
Fix a rare segmentation fault in the mmgetstatus command.
Fix a SIGBUS error that can occur during a mmap read on a snapshot file.
Fix a problem in which we see a flood of "failed to scrub vdisk" log message when GNR node experiences quorum loss. This is for ESS/GSS.
Fix a rare race between unlink, lookup and token revoke which causes kernel crash in d_revalidate.
This fix will make sure Ganesha request reference a valid GPFS filesystem.
Fix a system hang that can occur when a file system is suspended while doing a mmap.
This fix rejects unreasonable large requests to preallocate inodes immediately with ENOSPC.
Fix a directory rename issue with IW filesets that can occur if the rename target is an existing directory.
Fix a fault that can occur when restripe runs while the SG is not mounted on all NSD nodes.
This fix restricts the afmMaxParallelRecoveries config value from 0 to 128.
This fix removes the unnecessary error message "cannot open /proc/net/tcp6" when shutting down GPFS.
Fix a problem with not properly handling quotas in an AFM environment. This can occur when you have very large hard and soft limit values.
Fix a "exp(!sgP->isSGMgr())" assert that can occur when you delete a file system and then create a new file system with the same name at the same time.
Fix an err 112 that can show up in the mmfs logs when mmchnode --gateway is executed.
Fix a kernel crash that can occur while attempting to mount a loop device to a correspond file in a GPFS file system or while using a GPFS file system file as a LIO backend.
Address a problem where applyUpdates continues to run even if the fileset at the old primary is unlinked or the mmfs daemon has been shutdown.
Fix an outband resync failure that can occur if a recovery is triggered by deleting some files in a directory and the directory itself. This is an AFM/DR environment.
Fix rename conflicts that can occur in SW/DR filesets.
Update log code to prevent log recovery error when log file became illReplicated. This could happen on file system with -K set to NO and there is not enough disk space for full replication.
This fix will use new interface that will reduce multiple retries every time a lock is freed and there are multiple waiters for the lock.
Fix an assert that can occur with a DR fileset and the file system is suspended.
Fix bug that requires a large free space in /var/mmfs to run change commands.
Fix recovery failure err 17 when psnap0 deletion fails.
Fix a daemon assert that can occur in an AFM environment where the mmfsd daemon fails to start repeatedly with a DMAPI enabled filesystem at a gateway node.
Address a problem where trying to queue a writeSplit message to the helper gateway's queue can fail with an error 28 (E_NOSPAC).
Fix an issue which returns EACCESS(errno = 13) while running mmapplypolicy when there is a mounted NFS file system which has the same name with a GPFS file system.
A fastpath optimization defect can result in an internal error to be returned to the user when it is safe to continue without entering the fast path.
Install if you suffer from mmapplypolicy/tspolicy hanging after otherwise finishing all work.
cNFS: fix a problem with /usr/sbin/rpcinfo not found in SLES12 or later.
Fix a failure in Object Authentication configuration with Active Directory or LDAP. This fix is only required if Object is being configured with Active Directory or LDAP and DN of Swift service user(specified in --ks-swift-user) is more than 79 characters.
Fix a problem with ESS disk replacement in which the mmchcarrier command may wipe out the pdisk location code. The problem will prevent the subsequent mmchcarrier command to proceed without a valid location code.
Fix a problem in which a GPFS command may wrongly terminate another process.
Fix a rare deadlock problem caused by stream write(enableRepWriteStream=yes).
Update log recovery code to avoid GPFS daemon assert after detecting invalid directory block during log recovery. Code has been changed to log a FSSTRUCT error and fail the log recovery so offline mmfsck can be run on the file system.
Fix a mmfsd crashes (incompleteOk assertion), when the number of files in the committed directory doesn't match the number of files in CCR's file list in case of a new CCR file update request.
This update addresses the following APARs: IV94991 IV94992 IV94994 IV94995 IV94996 IV94997 IV94998 IV95015 IV95021 IV95230 IV95557 IV95643 IV95925 IV96037 IV96163.

Product/Component Name:	Platform:	Fix:
IBM Spectrum Scale	Linux390 64-bit RHEL Linux390 64-bit SLES Linux390 64-bit Ubuntu	Spectrum_Scale_Standard-4.2.3.2-s390x-Linux

Readme and Release notes for release 4.2.3.2 IBM Spectrum Scale 4.2.3.2 Spectrum_Scale_Standard-4.2.3.2-s390x-Linux Readme