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.

Add a new idea Subscribe
Status Not under consideration
Workspace Storage Scale (formerly known as GPFS)
Created by Guest
Created on Jan 9, 2018

RELATED IDEAS

Able to do mmcallback to stop the GPFS event, exemple prevent to unmount filesystems if services are still running

It would be nice to be able to configure a mmcallback in Spectrum Scale where the return code of the command run by the callback could stop the GPFS event.

Actually, from the IBM documentation, GPFS can make 3 differents things in a mmcallback :

--on error continue : GPFS just ignore the return code and continue the event

--on error quorumLoss : GPFS node will refrain from taking over the quorum

--on error shutdown : GPFS node will stop GPFS daemons if the return code is not zero.

I would like to have a feature like :

--on error stopevent : GPFS stop the actual event if return code is not zero.

With this feature, we could make a kind of validation for something and if the validation failed, then the command run by the callback will return a rc of 1, and GPFS then will just do nothing, the event will stop.

Idea priority Low
  • Guest
    Reply
    |     Sep 30, 2020

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - IBM Spectrum Scale
    Product - Spectrum Scale (formerly known as GPFS) - Public RFEs
    Component - Product functionality

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - IBM Spectrum Scale
    Product - Spectrum Scale (formerly known as GPFS) - Public RFEs
    Component - Technical Foundation

  • Guest
    Reply
    |     Sep 20, 2019

    We understand the value of this request. However, we think it will be very complex to implement safely without leaving a mount in some unknown state. Therefore it is not in scope for the foreseeable future

  • Guest
    Reply
    |     Jan 23, 2018

    Hello, thank you for taking time to analyse my suggestion.

    My actual needs is regarding these callback events : preUnmount and unmount.

    But I could see that these events could also benefit from this improvement : preMount, mount, preStartup and Startup.

    It make sense and can be very useful to configure automatic actions when GPFS is trigging on these events, because people could want to make some validations and verifications before GPFS start or before GPFS stop. So if user's validations are all OK, then user's script return 0 and GPFS continu to stop or start his process, but if something is not good, then user's script just return 1, and GPFS stop the actual event right there, to prevent undesired action.

    Thank you
    Eric Dubé

  • Guest
    Reply
    |     Jan 22, 2018

    This would be very complex to implement for all callbacks. Is there a specific list of commands that you are concerned with?

  • Guest
    Reply
    |     Jan 9, 2018

    Could also be used for other product that used GPFS as backend, like MQ or DB2 Purescale. Having such callback script & this RC option for callback, could prevent someone from stopping GPFS without first stopping MQ or DB2..

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.