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 Jun 9, 2026

RELATED IDEAS

Handle same directory renames and mkdir operations better

We have many instances where our users are concurrently attempting to perform mkdir and renames in the same parent directory accross many nodes.  These operations cannot be handled by GPFS fine-grain directory locking.  This results in every operation being queued waiting for an exclusive lock on the parent directory.  These perform very poorly.

We expected the performance impact of these operations should be limited to the parent directory.  However it seems that when there are many directories which are also concurrently being modified in this way then we do see overall performance impact to the file system.

GPFS also does not provide a way to determine which parent directories are impacted by these operations, making it very difficult to help users isolate where they are doing these operations in their applications.

It would greatly help with GPFS performance and overall usability if these operations are improved.  One possible suggestion would be to just ship the request for the rename or mkdir to the node that already has the exclusive lock on the directory.  This would allow one node to handle these operations and avoid the large sequential token revoke, update, revoke overhead for many nodes attempting these operations.

Idea priority High

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.