DELETE VOLUME DISCARDDATA=YES can unexpectedly remove data from another primary storage pool.

Content

Problem Summary: Data in a dedup pool exists as extents (areas of continuous storage) which can be referenced by multiple files. Using MOVE DATA to move dedup data from one primary pool to another primary pool can leave behind copies of extents that are still referenced by other files in the pool. These copies can be seen on the original volume using QUERY CONTENT FOLLOWLINKS=YES. Using DELETE VOLUME DISCARDDATA=YES for the original volume will delete the data from the original volume, which will create invalid links in the original primary pool. This is expected behavior. However, the DELETE VOLUME will also delete copies of the data that were moved to the other primary pool as well as any copies in copy pools. This is not expected behavior.

Who is Affected: You are affected if all of the following are true:

1. You use dedup storage pools (DEDUP=YES on DEFINE or UPDATE STGPOOL command).
2. You use MOVE DATA command to move data from one dedup pool to another primary pool, which can be dedup or non-dedup.
3. You use DELETE VOLUME DISCARDDATA=YES for volumes in dedup storage pools