IBM Support

Readme and Release notes for release 3.1.0.30 (GPFS) IBM General Parallel File System 3.1.0.30 GPFS-3.1.0.30-power-AIX Readme

Readme file for: GPFS-3.1.0.30-power-AIX
Product/Component Release: 3.1.0.30
Update Name: GPFS-3.1.0.30-power-AIX
Fix ID: GPFS-3.1.0.30-power-AIX
Publication Date: 29 July 2010
Last modified date: 29 July 2010

Installation information

Download location

Below is a list of components, platforms, and file names that apply to this Readme file.

Fix Download for AIX

Product/Component Name: Platform: Fix:
(GPFS) IBM General Parallel File System AIX 5.3
AIX 6.1
GPFS-3.1.0.30-power-AIX

Prerequisites and co-requisites

None

Known issues

  • - Problem discovered in earlier GPFS releases

    During internal testing, a rare but potentially serious problem has been discovered in GPFS. Under certain conditions, a read from a cached block in the GPFS pagepool may return incorrect data which is not detected by GPFS. The issue is corrected in GPFS 3.3.0.5 (APAR IZ70396) and GPFS 3.2.1.19 (APAR IZ72671). All prior versions of GPFS are affected.

    The issue has been discovered during internal testing, where an MPI-IO application was employed to generate a synthetic workload. IBM is not aware of any occurrences of this issue in customer environments or under any other circumstances. Since the issue is specific to accessing cached data, it does not affect applications using DirectIO (the IO mechanism that bypasses file system cache, used primarily by databases, such as DB2® or Oracle).

    This issue is limited to the following conditions:

    The issue is caused by a race between an application IO thread doing a read from a partially filled block (such a block may be created by an earlier write to an odd offset within the block), and a GPFS prefetch thread trying to convert the same block into a fully filled one, by reading in the missing data, in anticipation of a future full-block read. Due to insufficient synchronization between the two threads, the application reader thread may read data that had been partially overwritten with the content found at a different offset within the same block. The issue is transient in nature: the next read from the same location will return correct data. The issue is limited to a single node; other nodes reading from the same file would be unaffected.

Installation information

After you have downloaded a GPFS for AIX update package into any directory on your system, use the following section to install the fix package.

  • - Installing a GPFS update for AIX

    Complete these steps to install the fix package:

    1. Unzip and extract the BFF image(s) from the *.tar.gz file:

      gzip -d -c < filename > .tar.gz | tar -xvf -


    2. Verify the update's BFF image(s) in the directory.

      Normally, the BFF images in the directory would be similar to the following:
      Unnnnnn .gpfs.base.bff
      Unnnnnn .gpfs.msg.en_US.bff
      Unnnnnn .gpfs.docs.data.bff


      where nnnnnn represents the six (6) digits of the PTF number for the BFF image.

      For specific filenames, check the Readme for the GPFS update by clicking the "View" link for the update on the Download tab.


  • - Upgrading GPFS nodes

    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.

    1. 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.

Additional information

  • - Notices

    [June 9, 2010]

    A build error caused an issue with the DMAPI function in the GPFS 3.2.1-20 package that was released on May 27, 2010. The corresponding packages have now been replaced on the service download site.

    If you installed the May 27 GPFS 3.2.1-20 package and mounted a DMAPI-enabled file system while running GPFS 3.2.1-20 (fo r example, -z yes by means of the HSM features of TSM), please contact IBM Support. The replacement 3.2.1-20 package works a s designed, but does not fix a file system that was mounted with the problematic 3.2.1-20 package.

    Verify that you have the correct package installed by running the rpm -qi gpfs.base command. Make sure that the Bu ild Date is Mon 07 Jun 2010.

    [June 2, 2010]

    A build error caused an issue with the DMAPI function in the GPFS 3.3.0-6 package that was released on May 22, 2010. The corresponding packages have now been replaced on the service download site.

    If you installed the May 22 GPFS 3.3.0-6 package and mounted a DMAPI-enabled file system while running GPFS 3.3.0-6 (for example, -z yes by means of the HSM features of TSM), please contact IBM Support. The replacement 3.3.0-6 package works as d esigned, but does not fix a file system that was mounted with the problematic 3.3.0-6 package.

    Verify that you have the correct package installed by running the rpm -qi gpfs.base command. Make sure that the Bu ild Date is Thu 27 May 2010.

    [April 1, 2010]

    During internal testing, a rare but potentially serious problem has been discovered in GPFS. Under certain conditions, a read from a cached block in the GPFS pagepool may return incorrect data which is not detected by GPFS. The issue is corrected in GPFS 3.3.0.5 (APAR IZ70396) and GPFS 3.2.1.19 (APAR IZ72671). All prior versions of GPFS are affected.

    Click here for details.

    [December 17, 2009]

    Support for GPFS 3.1 has only been extended for AIX and Linux on POWER systems. Service updates will be made available for other Linux platforms, but support is not being extended.

    [November 9, 2009]

    GPFS 3.3.0-1 does not correctly operate with file systems created with GPFS V2.2 (or older). Such file systems can be identified by running "mmlsfs all -u": if "no" is shown for any file system, this file system uses the old format, and the use of GPFS 3.3.0-1 is not possible. GPFS 3.3.0-2 corrects this issue.

    [November 7, 2008]

    GPFS 3.2.1.7 contained a change that impacts TSM HSM recall process of files with stub size >0 causing hangs during recalls. To avoid this problem, the configuration parameter dmapiDataEventRetry has to be set to 'no' via command 'mmchconfig dmapiDataEventRetry=no -i '.

    [September 11, 2008]

    The 3.2.1-5 maintenance level had a data integrity problem using the mmap feature to write or update files on Linux and AIX. The 3.2.1-6 maintenance level is the recommended upgrade path from versions 3.2.0-0 through 3.2.1-4.

  • - Package information

    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.

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

    Update to Version:

    3.1.0.30

    Update from Version:

    3.1.0.0 through 3.1.0.29

    Update (tar file) contents:

    README
    changelog
    U811843.gpfs.docs.data.bff
    U824369.gpfs.msg.en_US.bff
    U829152.gpfs.base.bff

  • - Changelog for GPFS 3.1.x
    Notes

    Unless specifically noted otherwise, this history of problems fixed for GPFS 3.1.x applies for all supported platforms.

    Notices

    GPFS V3.1 maintenance levels 10 (GPFS-3.1.0.10) through 12 (GPFS-3.1.0.12) can not coexist with other maintenance levels.

    All nodes in the cluster must conform to one of these maintenance level compatibility restrictions:

    • All nodes must be at maintenance levels 1-9 or 13 and later (GPFS-3.1.0.1 thru GPFS-3.1.0.9 or GPFS-3.1.0.13 and later)

    Problems fixed in GPFS 3.1.0.30 [September 21, 2009]

    Problems fixed in GPFS 3.1.0.29 [July 14, 2009]

    Problems fixed in GPFS 3.1.0.28 [May 18, 2009]

    Problems fixed in GPFS 3.1.0.27 [March 30, 2009]

    Problems fixed in GPFS 3.1.0.26 [February 9, 2009]

    Problems fixed in GPFS 3.1.0.25 [December 18, 2008]

    Problems fixed in GPFS 3.1.0.24 [October 30, 2008]

    Problems fixed in GPFS 3.1.0.23 [September 18, 2008]

    Problems fixed in GPFS 3.1.0.22 [July 31, 2008]

    Problems fixed in GPFS 3.1.0.21 [June 19, 2008]

    Problems fixed in GPFS 3.1.0.20 [May 8, 2008]

    Problems fixed in GPFS 3.1.0.19 [March 27, 2008]

    Problems fixed in GPFS 3.1.0.18 [February 21, 2008]

    Problems fixed in GPFS 3.1.0.17 [December 20, 2007]

    Problems fixed in GPFS 3.1.0.16 [November 8, 2007]

    Problems fixed in GPFS 3.1.0.15 [October 1, 2007]

    Problems fixed in GPFS 3.1.0.14 [August 20, 2007]

    • This update addresses the following APARs:
      IZ01157 IZ01208 IZ01209 IZ01211 IZ01212 IZ01214 IZ01217 IZ01223 IZ01232 IZ01233 IZ01385 IZ01498 IZ01661 IZ01703 IZ01704 IZ01706 IZ01708 IZ01730 IZ01731 IZ01733 IZ01734 IZ01736 IZ01737 IZ01738 IZ01739 IZ01740 IZ01808 IZ01948 IZ01966 IZ01967 IZ01968 IZ01969 IZ02247 IZ02248 IZ02249 IZ02250 IZ02251 IZ02253 IZ02254 IZ02255 IZ02256 IZ02336

    Problems fixed in GPFS 3.1.0.13 [June 28, 2007]

    Problems fixed in GPFS 3.1.0.12 [May 17, 2007]

    Problems fixed in GPFS 3.1.0.11 [April 12, 2007]

Document information

More support for: General Parallel File System

Reference #: 00000147

Modified date: 29 July 2010