Skip to Main Content
IBM System Storage Ideas Portal


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).


Shape the future of IBM!

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:

Search existing ideas

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 your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

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.

Status Submitted
Created by Guest
Created on Feb 6, 2026

Improve handling of Snapshot (hidden FCMap in stopping state) cleanup

Currently, there isn't much to indicate that a FlashSystem is having a hard time doing it's VolumeGroup Snapshot cleanup.  If you look at the VG in the GUI, you'll see that the count of snapshots is greater than the number of snapshots that are actually listed in the GUI.  When I see this case (often for some of our arrays), it indicates that some previous snapshot is still getting cleaned up.  This can be discovered by listing the hidden fcmaps that are in a stopping state:
lsfcmap -showhidden -filtervalue status=stopping
Once I have these identified, I loop over them setting their cleanrate to something higher, and they are cleaned up quicky.  I just do 2 at a time, and set the clean-rate up to 150, paying attention to how busy the system actually is while doing the cleanup.

It seems like there could be some automation on the array that if we have old (arbitrary, but > 24 hours in my mind) fcmaps up their cleanrate to something that would resolve this in a more quickly fashion.

Idea priority Medium