Flashes (Alerts)
Abstract
IBM has identified an issue which can cause data to be written to the wrong location on the drive when using encrypted arrays on Storwize V7000 Gen2 systems. This will often result in systems logging 1691 and 1322 errors, and undetected data loss.
Content
IBM has identified an issue which can cause data to be written to the wrong location on the drive when using encrypted arrays on Storwize V7000 Gen2 systems.
- Attempts to read the data that was recently written will result in an undetected data loss, and the system return the stale data which should have been overwritten.
- Attempts to read the data from the "wrong" location will result in a 1322 error being logged and the data will be regenerated using parity where possible.
The Storwize products have a background process that validates whether the data on disk matches the parity on disk. If the background process detects that the data does not match the parity, for example when this issue occurs, then the system will log a 1691 error.
Data indicates that this issue is low probability, and normally occurs when the system is recovering from errors in the SAS network, however there is no way to avoid this issue without installing the fix.
This issue is resolved by APAR HU00820 in releases 7.4.0.5 and 7.5.0.2. If you have a system using encrypted arrays, IBM recommends that you upgrade as soon as possible.
If you have experienced a 1691 error please contact IBM support to resolve this error.
Was this topic helpful?
Document Information
Modified date:
28 March 2023
UID
ssg1S1005296