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
Restriping a file or a filesystem can be done for balance or to change location policy or both. However the -b option even when it gets to a relatively balanced state continues to reassign locations and move data when wadfg uses random placement even if the replica locations meet the existing policy. This is a waste of resources and means the restripefs runs for a long time. -l on restripefile does the same thing. However it's difficult to solve.
Propose to have two options.
1) Allow -b to terminate when the file system is relatively balanced.
2) Allow an option that only corrects for policy violations and doesn't move anything if the replica block meets the assigned policy. It should rearrange the block locations in the metadata if by rearrange the block order it meets the 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.
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
Customer is satisfied with 5.0 enhancements related to this issue.
Yes that works.
As of release 5.0, -b is considerably faster and moves fewer blocks compared to the 4.x release. Also, as of 5.0 the -b option, doesn't move the replica blocks as long as they meet the assigned policy and do not need to be moved for rebalanace. While this is not exactly the fix you asked for, does it address your concerns?