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

Storage Scale (formerly known as GPFS)

Showing 306

Overflow data placement

When creating a new filesystem with more than 1 pool, GPFS will guess where to put the file data. It would be nice if it was also capable of spillover to other pools, when the pool it guessed for here runs full: RULE 'default' SET POOL 'data' LIMI...
about 6 years ago in Storage Scale (formerly known as GPFS) 4 Not under consideration

support filesystem metadata migration to 4K-based NSDs

Provide a transparent (e.g. no downtime) mechanism to introduce NSDv2 4k-aligned metadata NSDs into filesystems created with NSDv1 format NSDs.
about 8 years ago in Storage Scale (formerly known as GPFS) 2 Not under consideration

API to return changed blocks since last backup

While Spectrum Scale synergy with Spectrum Protect (TSM) is great and completely adapted to the backup of a file system that is hosting a very large number of files (basically used as a file server) that are added every day and some of them being ...
about 8 years ago in Storage Scale (formerly known as GPFS) 2 Not under consideration

Expand mmrsync to accept filelist

mmrsync accepts the filenames only as parameters. Extend it to also accept a filename containing a list of files to sync.
about 8 years ago in Storage Scale (formerly known as GPFS) 3 Not under consideration

Use enterprise SATA drive in ECE

In our configuration, except SAS HDD/SSD and NVME, we also need to use enterprise SATA HDD/SSD as pdisk in ECE. These SATA drives can pass the ECE precheck for DpoFua and SCT ERC. The attachment is the list.
about 2 years ago in Storage Scale (formerly known as GPFS) 0 Not under consideration

Enable Case Sensitivity in SMB Protocol

Externalize Samba Option on mmsmb to enable Case sensitivity for customer.
over 6 years ago in Storage Scale (formerly known as GPFS) 2 Not under consideration

Dockers utilization for Spectrum Scale processes

Scale best practices recommends to have separate servers for Scale servers and Protocol Nodes. In ESS also is not supported to include Protocol Nodes inside the ESS nodes due to GNR resource contention. This implies to have almost four servers for...
over 8 years ago in Storage Scale (formerly known as GPFS) 3 Not under consideration

Data segregation with filesets link

The customer has a fileset. The application used is SAP netweaver.It runs on the cluster with one same uid/gid. The physical users are connected to this application remotelly and there is no UID/GID specific to them. One of the SAP transaction per...
almost 9 years ago in Storage Scale (formerly known as GPFS) 2 Not under consideration

Concurrent upgrades for Spectrum Scale Protocol Nodes

Currently, upgrades to Spectrum Scale are disruptive, documented to be 20 minutes per node. The stated reason is that SMB versions cannot co-exist, however, it is likely that not all upgrades introduce a new version of SMB.
over 6 years ago in Storage Scale (formerly known as GPFS) 7 Not under consideration

Protocol replication needs the ability to failover individual filesets for DR testing

Protocol replication has “all-or-nothing” failover/failback process. Cannot test DR for new exports. We need the ability to failover individual filesets for DR testing With “AFM-based DR” (which the protocols cluster DR is based on), and indeed fo...
almost 9 years ago in Storage Scale (formerly known as GPFS) 3 Not under consideration

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.