Upgrading to IBM Spectrum Scale 4.1.1.x from GPFS V4.1.0.x

Use the following information to upgrade from V4.1.0.x to V4.1.1.x.

For Linux:

Prior to upgrading GPFS on a node, all applications that depend on GPFS (For example, 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 file system 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 you are in the same directory as the files) :
For SLES or RHEL systems
```
rpm -Fvh gpfs*.rpm
```
For Debian systems
```
dpkg -i gpfs*.deb
```
You can verify the installation of the GPFS SLES or RHEL Linux RPMs on each node. To check that the software has been successfully installed, use the rpm command:
```
rpm -qa | grep gpfs
```
The system should return output similar to the following:
```
gpfs.gpl-4.1.1-1
gpfs.docs-4.1.1-1
gpfs.msg.en_US-4.1.1-1
gpfs.base-4.1.1-1
gpfs.gskit-8.0.50-40
```
If you have the GPFS Standard Edition or the GPFS Advanced Edition installed, you should also see the following line in the output:
```
gpfs.ext-4.1.1-1
```
If you have the GPFS Advanced Edition installed, you should also see the following line in the output:
```
gpfs.crypto-4.1.1-1
```
You can verify the installation of the GPFS Debian Linux packages on each node. To check that the software has been successfully installed, use the dpkg command:
```
dpkg -l | grep gpfs
```
The system should return output similar to the following:
```
ii gpfs.base 4.1.1-1     GPFS File Manager
ii gpfs.docs 4.1.1-1      GPFS Server Manpages and Documentation
ii gpfs.gpl 4.1.1-1         GPFS Open Source Modules
ii gpfs.gskit 8.0.50-40   GPFS GSKit Cryptography Runtime
ii gpfs.msg.en-us 4.1.1-1 GPFS Server Messages - U.S. English
```
If you have the GPFS Standard Edition or the GPFS Advanced Edition installed, you should also see the following line in the output:
```
ii gpfs.ext 4.1.1-1      GPFS Extended Features
```
If you have the GPFS Advanced Edition installed, you should also see the following line in the output:
```
ii gpfs.crypto 4.1.1-1    GPFS Cryptographic Subsystem
```
Recompile any GPFS portability layer modules you may have previously compiled using the mmbuildgpl command.

For AIX®:

Prior to upgrading GPFS on a node, all applications that depend on GPFS (For example, DB2) must be stopped. Any GPFS file systems that are NFS exported must be unexported prior to unmounting GPFS file systems.
To upgrade directly from 4.1.0.x to 4.1.1.x, you must put all Unnnnnn.gpfs*.bff images from 4.1.1.0 and 4.1.1.x in the same directory prior to running the installp command or SMIT.
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 installp command or via SMIT on the node. If you are in the same directory as the install packages, an example command might be:
```
installp -agXYd . gpfs
```

You can verify that the installation procedure placed the required GPFS files on each node by running the lslpp command

lslpp -l gpfs\*

The system should return output similar to the following:

Fileset                 Level      State        Description
----------------------------------------------------------------------------
Path: /usr/lib/objrepos
gpfs.base              4.1.1-1 COMMITTED GPFS File Manager
gpfs.crypto            4.1.1-1 COMMITTED GPFS Cryptographic Subsystem
gpfs.ext               4.1.1-1 COMMITTED GPFS Extended Features
gpfs.gskit            8.0.50.40 COMMITTED GPFS GSKit Cryptography Runtime
gpfs.msg.en_US         4.1.1-1 COMMITTED GPFS Server Messages - U.S. English
Path: /etc/objrepos 
gpfs.base              4.1.1-1 COMMITTED GPFS File Manager
Path: /usr/share/lib/objrepos
gpfs.docs.data         4.1.1-1 COMMITTED GPFS Server Manpages and
Documentation

The output that is returned on your system can vary depending on if you have the GPFS Express Edition, GPFS Standard Edition, or GPFS Advanced Edition installed.

For Windows:

Downloaded the GPFS 4.1.1-x update package into any directory on your system.
Note: This update requires a prior level of GPFS version 4.1.x on your system. In such a case, you need to simply uninstall the previous 4.1.x level and proceed with installing this upgrade. Upgrading from a prior 4.1 level does not require installing the GPFS license package again. However if you are upgrading directly from version 3.5 or prior (any level), or installing version 4.1 for the first time on your system, you must first install the GPFS license package (gpfs.base-4.1-Windows-license.msi) before installing this update.
Extract the contents of the ZIP archive so that the .msi file it includes is directly accessible to your system.
Uninstall the system's current version of GPFS using the Programs and Features control panel. If prompted to reboot the system, do this before installing the update package.