Skip to Main Content
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.

Status Submitted
Created by Guest
Created on Sep 9, 2025

allow s3 nooba to upload user files to gpfs

we have setup mmces S3 to allow users to write into an immutable fileset (Noncompliant Mode) for long term archiving their data.

Listing and reading files from or even removing them in the fileset via S3 works as expected. But an upload of new data failes with "error 403 not Permitted". 

We have followed the logs and found out that nooba-core, when uploading file to the filesystem, creates a hard link at some point in the process. Probably to continue uploads in case of interruption. As creating these hard links are prohibited in GPFS inside immutable filesets the whole upload fails.

It could be solved by changing uploading data without using hard-links in the process, or by introducing a special noncompliant mode 
 

Idea priority High