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.
See this idea on ideas.ibm.com
The noDiskspace callback is triggered on several occasions, one being an inodespace running out of inodes. At that point n time the filespace is already full and users see "no space on device" errors. We'd need a similar callback that triggers earlier. Or, alternatively a way to customize this callback to trigger at a certain mark BEFORE the inodes are exhausted.
An alternative was some kind of automatism that increased the maxInodes value on demand.
There's the lowDiskSpace callback but this is a) not supporting filesets and b) depending on the current policy.
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.
I think this is not the same. You can activate --auto-inode-limit only for the whole filesystem but not individually per fileset. So there might/will be situations where some filesets should not be auto-extended while others should. This could be solved with a callback but not with --auto-inode-limit
In scaale 5.1.4 we introduced --auto-inode-limit file system config option , you can enable this filesystem option to avoid running into out of inode situation until it actually hits the physical storage limit.