We deeply regret to inform GPFS users that the 22.214.171.124 service update contains a serious flaw. When parsing some RPCs sent by nodes running GPFS 126.96.36.199 or earlier, the code in 188.8.131.52 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 184.108.40.206 and pre-220.127.116.11 nodes are present in the same cluster, accessing the same file systems. If you are considering upgrading GPFS from a pre-18.104.22.168 level (including 3.3.0.X), do not upgrade to the unpatched 22.214.171.124. Clusters running only 126.96.36.199 or later nodes, including 188.8.131.52, are not affected.
The problem will be fixed in 184.108.40.206. An efix for 220.127.116.11 is also available via IBM Service.
This topic has been locked.
1 reply Latest Post - 2012-05-02T18:48:32Z by firstname.lastname@example.org
Pinned topic Backward compatibility problem in GPFS 18.104.22.168
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-05-02T18:48:32Z at 2012-05-02T18:48:32Z by email@example.com
firstname.lastname@example.org 060000T9GF214 PostsACCEPTED ANSWER
Re: Backward compatibility problem in GPFS 22.214.171.124012-05-02T18:48:32Z in response to email@example.comTo expand on the previous post: both 126.96.36.199 and 188.8.131.52 levels contain the same backward compatibility issue. All of the 184.108.40.206 warnings and workarounds also apply to 220.127.116.11.