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.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Storage
Product - IBM System Storage SAN Volume Controller (SVC) / Spectrum Virtualize
For recording keeping, the previous attributes were:
Brand - Tivoli
Product family - Storage
Product - IBM System Storage SAN Volume Controller (SVC) / Spectrum Virtualize
We have had problems during the POC where the vdisk mirror made the SVC pause IOs for a long time, because it took too long to recognize that one Subsystem was undergoing maintenance.
Currently there is no command to suspend the vdisk mirror, so that no disk smoothing and mirrorwritepriority timeouts will need to elapse before a copy is take offline. You can delete a copy, but that would require to re-sync all the data after the maintenance, so what they were asking for is a simply suspend command, which immediately marks one vdisk copy offline and the other one will be the working copy. If you run this command for all vdisks copies that are backed by the storage system that you are planning maintenance for, SVC will not need to pause IO when the write cache is full, and the de-stage operations has to time out (with disk smoothing 180 seconds) before he mdisk group is taken offline.
An alternative would be to have a command to take a mdisk group offline, which would at the end result in the same result for the customer, but actually would be simpler to use.
If you need any more information please send me an e-mail with your questions