Topic
2 replies Latest Post - ‏2012-07-21T12:35:20Z by gpfs@us.ibm.com
gpfs@us.ibm.com
gpfs@us.ibm.com
209 Posts
ACCEPTED ANSWER

Pinned topic internal testing on unsupported config has identified a potential DI issue

‏2012-07-18T18:42:40Z |
In internal testing on an unsupported configuration, IBM has identified a potential data integrity issue in GPFS 3.4.0.9 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 3.4.0.15 (APAR IV24937) and GPFS 3.5.0.3 (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 3.4.0.15 or GPFS 3.5.0.3 as soon as they are available. Alternatively, customers may contact IBM Service and request an ifix for their installed GPFS version.
Updated on 2012-07-21T12:35:20Z at 2012-07-21T12:35:20Z by gpfs@us.ibm.com
  • nhardt
    nhardt
    1 Post
    ACCEPTED ANSWER

    Re: internal testing on unsupported config has identified a potential DI issue

    ‏2012-07-18T19:53:11Z  in response to gpfs@us.ibm.com
    Can 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?

    Thank you.
    • gpfs@us.ibm.com
      gpfs@us.ibm.com
      209 Posts
      ACCEPTED ANSWER

      Re: internal testing on unsupported config has identified a potential DI issue

      ‏2012-07-21T12:35:20Z  in response to nhardt
      Even 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 3.4.0.9 and later releases of GPFS 3.4, or any level of GPFS 3.5 prior to GPFS 3.5.0.3. 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.