If a Storwize V7000 or SAN Volume Controller FlashCopy mapping is started on Volumes greater than 2TB in size, this will result in the FlashCopy operation writing incorrect data to the target Volume. The target Volume will therefore not contain the same data as the source Volume.
An issue has been discovered that will result in incorrect data being written to FlashCopy target Volumes greater than 2TB (2,199,023,255,552 bytes) in size.
Data on the source Volume will be unaffected by this issue. Any FlashCopy replicated Volumes less than 2TB in size will also be unaffected by this issue.
Customers are strongly advised not to perform any FlashCopy operations on Volumes greater than 2TB in size, until the fix has been applied.
Customers should also be aware that any previously created FlashCopy target Volumes greater than 2TB in size will have incorrect data on them, and should be treated as inconsistent with the original source data.
This issue is fixed by APAR IC76806 in the 184.108.40.206 and 220.127.116.11 PTF releases.
Customers using incremental FlashCopy replication of Volumes greater than 2TB, should be aware that simply installing this fix will not restore consistency between source and target Volumes. Any incremental FlashCopy mappings will need to be deleted and recreated after the fix has been applied, to ensure that all incremental target Volumes are fully re-populated with the correct source Volume data.
Customers with non-incremental FlashCopy mappings greater than 2TB simply need to restart these mappings after the upgrade has been applied, in order to achieve a consistent target Volume copy.
Please refer to the What's new in the IBM System Storage SAN Volume Controller Information Center for more information on SVC Terminology changes.
17 June 2018