Package Information

GPFS 3.2.1-20 Update for Linux 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 are a mix of normal RPM
images that 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 RPMs are installed, you have successfully updated your GPFS product.


Known Issues

1. On SLES 10 for POWER

 a. /etc/init.d/running-kernel that ships with pre SLES10 SP1 kernel-source
    rpms contains a bug that results in the wrong set of files being copied
    to the kernel source tree. This bug will be fixed with SLES10 SP1. If the
    official fix is unavailable, the following change should also address the
    problem:   
	--- running-kernel.orig 2006-10-06 14:54:36.000000000 -0500 
	+++ /etc/init.d/running-kernel  2006-10-06 14:59:58.000000000 -0500 
	@@ -53,6 +53,7 @@     
 	 arm*|sa110)    arch=arm ;;      
	 s390x)  arch=s390 ;;      
	 parisc64)  arch=parisc ;; 
	+ ppc64)     arch=powerpc ;;      
	esac      
	# FIXME: How to handle uml? 

 b. The gpfs.base 3.2.0-0 rpm must be installed using the rpm --nopre flag
    BEFORE any updates can be applied.

2. The GPFS required level of Korn Shell for SLES 10 support is version 
   ksh-93r-12.16 and can be obtained in the following way:

   After registering at:
   https://secure-www.novell.com/center/ICSLogin/?%22https://secure-www.novell.com/center/regadmin/jsps/home_app.jsp%22

   Use the following architecture-specific link:
   https://you.novell.com/update/ppc/update/SUSE-SLES/10/PTF/43ed798d45b1ce66790327fe89fb3ca6/20061201


Update to Version:

   3.2.1-20

Update from Version:

   3.2.0-0
   3.2.0-1
   3.2.0-2
   3.2.0-3
   3.2.1-1
   3.2.1-2
   3.2.1-3
   3.2.1-4
   3.2.1-5
   3.2.1-6
   3.2.1-7
   3.2.1-8
   3.2.1-9
   3.2.1-10
   3.2.1-11
   3.2.1-12
   3.2.1-13
   3.2.1-14
   3.2.1-15
   3.2.1-16
   3.2.1-17
   3.2.1-18
   3.2.1-19

Update (tar file) contents:

   README
   changelog
   gpfs.base.3.2.1-20.sles9.ppc64.update.rpm
   gpfs.docs.3.2.1-20.noarch.rpm
   gpfs.gpl.3.2.1-20.noarch.rpm
   gpfs.msg.en_US.3.2.1-20.noarch.rpm

Install the corrective service package

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

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

   gpfs.base.3.2.1-20.sles9.ppc64.update.rpm
   gpfs.docs.3.2.1-20.noarch.rpm
   gpfs.gpl.3.2.1-20.noarch.rpm
   gpfs.msg.en_US.3.2.1-20.noarch.rpm

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 RPM command as follows:

      rpm -U gpfs.base-3.2.1-20.sles9.ppc64.update.rpm
      rpm -U gpfs.docs-3.2.1-20.noarch.rpm
      rpm -U gpfs.gpl-3.2.1-20.noarch.rpm
      rpm -U gpfs.msg.en_US-3.2.1-20.noarch.rpm

   d) Check the GPFS FAQ to see if any additional images or patches are required
      for your Linux installation:

      http://publib.boulder.ibm.com/infocenter/clresctr/topic/com.ibm.cluster.gpfs.doc/gpfs_faqs/gpfs_faqs.html

   e) Recompile any GPFS portability layer modules you may have previously
      compiled. The recompilation and installation procedure is outlined in
      the following file:

      /usr/lpp/mmfs/src/README
