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 Submitted
Workspace Storage Scale (formerly known as GPFS)
Created by Guest
Created on Nov 7, 2024

RELATED IDEAS

Recover failed Ganesha node - which mark with F flag, without reboot.

Hi

We had NFS Ganesha node that failed - but we did not able to recover it , only reboot solve it.


Sysmon attempted to remove the F flag three times, but all attempts to acquire the lock failed.
As a result, the node remained in a failed state despite being healthy.
Restarting the node allowed the process to retry successfully once the lock became available.

NFS failure: RPC null checks and the stat checks (collects IO number 2 times and if its the same, the test fails) both failed. thats why nfs_not_active. This was fixed soon.
why node stayed in failed state even NFS was healthy: But to remove Failed state we need a fail-over lock and we didn't get it, it tries 3 times. Later when the lock was available, we had already exhausted our tries. And this is working as designed. But ideally we may want to redesign this.

Idea priority Medium

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.