Package Information

GPFS 3.1.0.22 Update for AIX 5L on System p (POWER servers)

Description

The update images listed below and contained in the tar image with this README
are maintenance packages for GPFS. The update images can be directly applied
to your system.

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

Once all BFFs are installed, you have successfully updated your GPFS product.


Update to Version:

   3.1.0.22


Update from Version:

   3.1.0.0
   3.1.0.1
   3.1.0.2
   3.1.0.3
   3.1.0.4
   3.1.0.5
   3.1.0.6
   3.1.0.7
   3.1.0.8
   3.1.0.9
   3.1.0.10
   3.1.0.11
   3.1.0.12
   3.1.0.13
   3.1.0.14
   3.1.0.15
   3.1.0.16
   3.1.0.17
   3.1.0.18
   3.1.0.19
   3.1.0.20
   3.1.0.21

Update (tar file) contents:

   README
   changelog
   U820324.gpfs.base.bff
   U813890.gpfs.msg.en_US.bff
   U811843.gpfs.docs.data.bff

Install the corrective service package

After you have downloaded the GPFS 3.1.0.22 update package into any directory on
your system, follow these steps to install the fix package:

1. Verify this update's BFF images in the directory. the list of BFF images in
   this directory should now be

   U820324.gpfs.base.bff
   U813890.gpfs.msg.en_US.bff
   U811843.gpfs.docs.data.bff

2. Follow the installation and migration instructions in your GPFS Concepts,
   Planning and Installation Guide.

   NOTE: In the below instructions, node-by-node upgrade cannot be used
   to migrate from GPFS 2.3 to later releases. For example, upgrading
   from 2.3.x to 3.1.y requires complete cluster shutdown, upgrade
   install on all nodes and then cluster startup.

   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.

   a) Prior to upgrading GPFS on a node, all applications that depend on
      GPFS (e.g. Oracle) must be stopped.  Any GPFS file systems that are
      NFS exported must be unexported prior to unmounting GPFS file systems.
      If tracing was turned on, then tracing must be turned off before
      shutting down GPFS as well.

   b) 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.

   c) Upgrade GPFS using the installp command or via SMIT on the node.
