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.
Dear SpectrumScale team,
even after 5 years, this idea is still listed as "Not under consideration".
The former guest comment about "significant performance improvements for mmdsh" is of no help either, since running "
mmdsh -N all lsof +D /path/to/FilesetJunctionPoint/
" is still unfeasible for large and remote clusters.As the filesystem manager ('
sgmgr
') needs to know anyhow which files/directories are open on arbitrary (remote cluster) nodes: why can't we ask this central component directly, on which nodes a certain fileset/directory has open handles...?Is SpectrumScale a distributed file system or not - and in the case it is, it should be able to directly answer such "questions about distributed use" without clumsy workarounds like "
mmdsh
".It would be no problem if the output only were the internal node identfier like
<c2n630>
, as this could be resolved with "mmdiag --network
".Please re-consider this suggestion - it would be a great help in case of
Thanks!
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
There is a significant planned performance improvement in mmdsh -n all targeted for 5.0.3. We ask that you evaluate that feature (either in Beta or GA) and let us know if it addresses the requirement sufficiently.