Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
1 reply Latest Post - ‏2012-05-02T18:48:32Z by gpfs@us.ibm.com
gpfs@us.ibm.com
gpfs@us.ibm.com
217 Posts
ACCEPTED ANSWER

Pinned topic Backward compatibility problem in GPFS 3.4.0.12

‏2012-04-30T17:11:59Z |
We deeply regret to inform GPFS users that the 3.4.0.12 service update contains a serious flaw. When parsing some RPCs sent by nodes running GPFS 3.4.0.6 or earlier, the code in 3.4.0.12 incorrectly processes certain data structures, resulting in GPFS crashes. The most typical symptom of this issue is the "((diskNum > 0) && (diskNum <= sgP->getNDisks())" assert in LogFile::append, although other symptoms are possible. The problem occurs most readily when metadata is not replicated (mmlsfs shows -m 1); metadata replication mitigates the problem to a large extent, but not completely. Full data and metadata replication would prevent the problem from happening.

The problem is limited to the scenarios where 3.4.0.12 and pre-3.4.0.7 nodes are present in the same cluster, accessing the same file systems. If you are considering upgrading GPFS from a pre-3.4.0.6 level (including 3.3.0.X), do not upgrade to the unpatched 3.4.0.12. Clusters running only 3.4.0.7 or later nodes, including 3.4.0.12, are not affected.

The problem will be fixed in 3.4.0.13. An efix for 3.4.0.12 is also available via IBM Service.

Sincere apologies,

GPFS team
Updated on 2012-05-02T18:48:32Z at 2012-05-02T18:48:32Z by gpfs@us.ibm.com
  • gpfs@us.ibm.com
    gpfs@us.ibm.com
    217 Posts
    ACCEPTED ANSWER

    Re: Backward compatibility problem in GPFS 3.4.0.12

    ‏2012-05-02T18:48:32Z  in response to gpfs@us.ibm.com
    To expand on the previous post: both 3.4.0.12 and 3.5.0.1 levels contain the same backward compatibility issue. All of the 3.4.0.12 warnings and workarounds also apply to 3.5.0.1.

    Regards,

    GPFS team