Flashes (Alerts)
Abstract
IBM has identified an issue in IBM Spectrum Scale (GPFS) V4.2.0.0 through 4.2.3.20 (ESS 4.0 through 5.2.9), and V5.0.0.0 through 5.0.4.2 (ESS 5.3 through 5.3.5.1) levels, in which the concurrent use of mmap write and compression operations may cause the data in data blocks being compressed to be corrupted.
Content
Generally, the compression operation will be skipped or fail if a regular file is already memory-mapped. Conversely, if the file has already been compressed before a memory-map operation happens on the same file, the data area being mmap written will first be decompressed. However, when a regular file is being compressed and is then memory-mapped, the mmap read operation could page the data into the Operating System (OS) page-cache before a data block is compressed. If an mmap write operation on the just paged-in page happens at the same time as that data block is being compressed, the newly written data in the page-cache may be written to that compressed data block directly without a decompression being attempted. Such a compressed data block containing some uncompressed data would result in decompression failure with an EIO error being returned in most cases to users or applications. Although possible but less likely, corrupted data undetected by users may be returned, as damaged compression data could be mistakenly interpreted by the decompression process. In addition, an FSErrBadCompressBlock file system structure error may be logged into the system log file.
- For IBM Spectrum Scale V5.0.0.0 through 5.0.4.2 (ESS 5.3 through 5.3.5.1), reference APAR IJ22718
- For IBM Spectrum Scale V4.2.0.0 through 4.2.3.20 (ESS 4.0 through 5.2.9), reference APAR IJ22922
Was this topic helpful?
Document Information
Modified date:
21 April 2020
UID
ibm15736753