In internal testing on an unsupported configuration, IBM has identified a potential data integrity issue in GPFS 188.8.131.52 and later releases of GPFS 3.4, and with GPFS 3.5. This issue has not, to IBM's knowledge, been experienced in the field. The issue occurs only when writing via NFS to a GPFS node running on the Linux operating system. This issue may manifest as either a data loss issue from a transient read error, returning zeros rather than the expected data, or as incorrect data returned following a write that is applied to the wrong file.
The fix for this issue will be included in GPFS 184.108.40.206 (APAR IV24937) and GPFS 220.127.116.11 (APAR IV24942). While IBM can not rule out the possibility that this problem may impact any customer writing via NFS in Linux GPFS environments at the stated levels, empirical evidence suggests that the likelihood of customers encountering this issue is quite limited. To avoid this issue customers should upgrade to GPFS 18.104.22.168 or GPFS 22.214.171.124 as soon as they are available. Alternatively, customers may contact IBM Service and request an ifix for their installed GPFS version.
This topic has been locked.
2 replies Latest Post - 2012-07-21T12:35:20Z by email@example.com
Pinned topic internal testing on unsupported config has identified a potential DI issue
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-07-21T12:35:20Z at 2012-07-21T12:35:20Z by firstname.lastname@example.org
nhardt 270003NRWK1 PostACCEPTED ANSWER
Re: internal testing on unsupported config has identified a potential DI issue2012-07-18T19:53:11Z in response to email@example.comCan you elaborate more on the specific unsupported configuration where the issue was found, and perhaps provide some information that will help others determine whether or not they are are affected?
firstname.lastname@example.org 060000T9GF214 PostsACCEPTED ANSWER
Re: internal testing on unsupported config has identified a potential DI issue2012-07-21T12:35:20Z in response to nhardtEven though this was detected on an unsupported configuration, IBM cannot rule out the possibility that this problem may impact any customer writing via NFS in Linux GPFS environments using GPFS 126.96.36.199 and later releases of GPFS 3.4, or any level of GPFS 3.5 prior to GPFS 188.8.131.52. Therefore, IBM recommends that all GPFS customers running the affected code levels apply this fix in PTF or ifix form as soon as is possible. Customers may contact IBM Service and request an ifix for their installed GPFS version.