Applications or Operating Systems Which Use Persistent Reserves May Suffer Loss of Access to Data When Upgrading to Some Versions of V6.4.0 and V6.4.1 From V6.3.0 and earlier
An issue has been identified which causes SAN Volume Controller and Storwize V7000 systems to mishandle SCSI-3 Persistent Reserves during upgrades from V6.3.0 and earlier to V6.4.0.x, V18.104.22.168, V22.214.171.124 and V126.96.36.199. Storwize V7000 Unified upgrades from 1.3 to 1.4 are also exposed to this issue. Any application or operating system which uses Persistent Reserves may suffer a loss of access to data during the upgrade.
Some systems may be able to automatically clear the mishandled Persistent Reserves and take new Persistent Reserves. These systems will not experience a loss of access to data.
The following systems are known to be exposed to this issue, however any systems using SCSI-3 Persistent Reserves may be affected if they are unable to automatically recover.
- Microsoft Clustering
- Some AIX configurations
Upgrades from SVC or V7000 V6.4 or V7000 Unified V1.4 to later releases are not exposed to this issue.
This issue is resolved by APAR IC89355 in V188.8.131.52.
This issue will be resolved in a future release of Storwize V7000 Unified.
|Storage Virtualization||SAN Volume Controller||6.4||SAN Volume Controller||6.4|
|Disk Storage Systems||IBM Storwize V7000 Unified (2073)||1.4||IBM Storwize V7000||1.4|