Re: [gpfsug-discuss] FW: [EXTERNAL] FLASH: IBM Spectrum Scale (GPFS) V4.1 and 4.2 levels: network reconnect function may result in file system corruption or undetected file data corruption (2017.10.09

Richard, I see that 4.2.3-4 efix2 has two defects, 1032655 (IV99796) and 1020461 (IV99675), and both these fixes are included in 4.2.3.5 . Regards, Felipe Felipe Knop k...@us.ibm.com GPFS Development and Security IBM Systems IBM Building 008 2455

Re: [gpfsug-discuss] FW: [EXTERNAL] FLASH: IBM Spectrum Scale (GPFS) V4.1 and 4.2 levels: network reconnect function may result in file system corruption or undetected file data corruption (2017.10.09

Hi Felipe On a related note, would everything in 4.2.3-4 efix2 be included in 4.2.3-5? In particular the previously discussed around defect 1020461? There was no APAR for this defect when I last looked on 30th August. Thanks Richard From: gpfsug-discuss-boun...@spectrumscale.org

Re: [gpfsug-discuss] FW: [EXTERNAL] FLASH: IBM Spectrum Scale (GPFS) V4.1 and 4.2 levels: network reconnect function may result in file system corruption or undetected file data corruption (2017.10.09

Tomasz, The fix (APAR 1IJ00398) has been included in 4.2.3.5, despite the APAR number having been omitted from the list of fixes in the PTF. Regards, Felipe Felipe Knop k...@us.ibm.com GPFS Development and Security IBM Systems IBM Building 008 2455

Re: [gpfsug-discuss] FW: [EXTERNAL] FLASH: IBM Spectrum Scale (GPFS) V4.1 and 4.2 levels: network reconnect function may result in file system corruption or undetected file data corruption (2017.10.09

Thank you for the information. I was checking changelog for GPFS 4.2.3.5 standard edition, but it does not mention APAR IJ00398: https://www-01.ibm.com/support/docview.wss?rs=0=isg43555 This update addresses the following APARs: IJ00031 IJ00094 IJ00397 IV99611 IV99675 IV99676 IV99677

Re: [gpfsug-discuss] FW: [EXTERNAL] FLASH: IBM Spectrum Scale (GPFS) V4.1 and 4.2 levels: network reconnect function may result in file system corruption or undetected file data corruption (2017.10.09

Tomasz, Though the error in the NSD RPC has been the most visible manifestation of the problem, this issue could end up affecting other RPCs as well, so the fix should be applied even for SAN configurations. Regards, The Spectrum Scale (GPFS) team

Re: [gpfsug-discuss] FW: [EXTERNAL] FLASH: IBM Spectrum Scale (GPFS) V4.1 and 4.2 levels: network reconnect function may result in file system corruption or undetected file data corruption (2017.10.09

Hi, From what I understand this does not affect FC SAN cluster configuration, but mostly NSD IO communication? Best regards, Tomasz Wolski From: gpfsug-discuss-boun...@spectrumscale.org [mailto:gpfsug-discuss-boun...@spectrumscale.org] On Behalf Of Ben De Luca Sent: Wednesday, October 11, 2017

Re: [gpfsug-discuss] FW: [EXTERNAL] FLASH: IBM Spectrum Scale (GPFS) V4.1 and 4.2 levels: network reconnect function may result in file system corruption or undetected file data corruption (2017.10.09

Lyle thanks for the update, has this issue always existed, or just in v4.1 and 4.2? It seems that the likely hood of this event is very low but of course you encourage people to update asap. On 11 October 2017 at 00:15, Uwe Falke wrote: > Hi, I understood the failure to

Re: [gpfsug-discuss] FW: [EXTERNAL] FLASH: IBM Spectrum Scale (GPFS) V4.1 and 4.2 levels: network reconnect function may result in file system corruption or undetected file data corruption (2017.10.09

Hi, I understood the failure to occur requires that the RPC payload of the RPC resent without actual header can be mistaken for a valid RPC header. The resend mechanism is probably not considering what the actual content/target the RPC has. So, in principle, the RPC could be to update a data

Re: [gpfsug-discuss] FW: [EXTERNAL] FLASH: IBM Spectrum Scale (GPFS) V4.1 and 4.2 levels: network reconnect function may result in file system corruption or undetected file data corruption (2017.10.09

does this corrupt the entire filesystem or just the open files that are being written too? One is horrific and the other is just mildly bad. On 10 October 2017 at 17:09, IBM Spectrum Scale wrote: > Bob, > > The problem may occur when the TCP connection is broken between two