This portal is to open public enhancement requests against IBM System Storage products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Thank you for submitting this enhancement request. We do have some work in progress to eliminate DMAPI “recall storms” from concurrent stub file deletions with snapshot and this enhancement should reduce recalls needed on file deletion, but not in the way it described in your request.
Thinking more about the current implemntation leaves me with an unpleasent feeling because there's a time gap (e.g. between the migration and the transparent recall on overwrite of the original/migrated file) where the disk space is freed. So theoretically it can happen that during that time gap the disk gets filled up by other tasks and the recall cannot be done anymore. In that case one's left with a broken snapshot. This situation would completely vanish with the proposed idea, too.
Also we have a reversal of the filesystem behaviour compared to non-HSM gpfs filesystems. On a non-HSM fs deleting the original file will not free any space as long as there's at least one snapshot. On an HSM fs deleting the original file will instead increase disk usage. This difference would also vanish with the proposed idea.