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 18, 2025

RELATED IDEAS

Prevent attribute changes by non-root users

We are running a big filesystem that controls file access by (nfsv3) ACLs. The ACLs are carefully crafted to ensure the desired file accesses for the data. As ACLs are not directly visible via ls (there's only the tiny + character) users tend to make wrong assumptions about the general accessability of files and run chmod, often recursively. Some users also try to run setfacl. This often leads to the opposite of the intention, making files unavailable for other users. And this causes unneccessary work for the administrators

So the idea is to add one or multiple configuration setting(s) to prevent (non-root) users from changing file permissions, ACLs and possibly ownership by making the system calls behind the respective commands no-ops. It should be configurable to either report success but not change anything or to report failure (depending on the workflow one or the other may be preferable). Being able to set this per fileset would be a further improvement.

Maybe this could be implemented by a special ACL. That way it could be activated even for single files.

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.