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
Today, mmclone can be used to effectively provide a read-only snapshot of a single file (mv origfile snapfile ; mmclone snap snapfile ; mmclone copy snapfile origfile). But to clean up the snapshot when it is no longer needed requires mmclone split (followed by rm snapfile). This method forces any unmodified blocks between the two files to be duplicated into the writable clone, and for large files can take a while. This is made worse by the fact that the parent file is just going to be immediately deleted, so a more efficient mechanism to unlink the blocks would be ideal.
There are multiple ways this might be addressed, including:
- implement "mmclone unlink" to drop a parent file which only has one direct child by unlinking shared blocks and deleting blocks belonging only to the parent.
- implement a different command to create/delete a readonly copy-on-write clone of an existing file, which inverts the mmclone design (in which a RO file parents a RW file) into one where a RW file incepts a new RO file. It would be acceptable for our use case if only one RO file snapshot could exist for a given file at a time, but other customers might disagree and advocate a more flexible solution.
As always, we expect the actual implementation will be determined by IBM development.
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