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 Not under consideration
Workspace Storage Scale (formerly known as GPFS)
Created by Guest
Created on Jun 22, 2019

RELATED IDEAS

Attach an existing directory to a fileset

Was discussing root admin with ibm dev Germany and realized that some commands seem never to have finished development. You have two commands one to create a fileset and another to link it to a directory. But the link one requires the directory to be created.

In the AI/analytics world users are constantly creating new project directories. It would be good if mmlinkfileset could be done retroactively after the mkdir. I suspect this was always the intention otherwise why have a create and link steps. I also suspect original intention was to allow the same fileset to be linked to more than one directory to create a policy class of directories. Don't need to go that far but adding a fileset to an existing directory would be very useful and it's just a metadata change. All policies apply from the point of being applied to the fileset if a directory is associated with a fileset at a later date then placement policies, etc would be applied from that point not retroactively. This is no different than changing a placement policy on a fileset.

Directory classes associated to a fileset would be nice too.

Idea priority Medium
  • Guest
    Reply
    |     Nov 9, 2020

    We will be addressing the underlying requirement by increasing fileset scalability

  • Guest
    Reply
    |     Sep 30, 2020

    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

  • Guest
    Reply
    |     Jun 28, 2019

    So step by step.

    Basic scenario:
    File system /filesystem; Device: filesys
    User does: mkdir /filesystem/projectlinkfileset

    Later administrator does:
    mmcrfileset projectlinkfileset
    mmlinkfileset filesys projectlinkfileset -J /filesystem/projectlinkfileset

    Now we can apply policies to the directory. The current process requires:

    mv /filesystem/projectlinkfileset /filesystem/projectlinkfileset-bkup
    mmcrfileset projectlinkfileset
    mmlinkfileset filesys projectlinkfileset -J /filesystem/projectlinkfileset
    mv /filesystem/projectlinkfileset-bkup/* /filesystem/projectlinkfileset
    rm /filesystem/projectlinkfileset-bkup

    That may seem small but in a large, 24*7*366 operational system it can be hard to have the directory temporarily disappear or for it to be suddenly empty. Automated scripts break, etc.

    The current rules mean that you don't actually need separate create fileset and link fileset steps. You could the create and link in one step. So it would appear that the current rules were introduced due to an unforeseen restriction. So the question becomes what was that restriction and does it still exist. Which led me to the following alternate scenario:

    More capable scenario but this would also break the rule that a fileset can only be linked to a single file system object:

    User does:
    mkdir /filesystem/projectlinkfileset
    mkdir /filesystem/projectlinkfileset/dev
    mkdir /filesystem/projectlinkfileset/qa
    mkdir /filesystem/projectlinkfileset/release

    Later administrator does:
    mmcrfileset projectlinkfilesetdevqa
    mmlinkfileset filesys projectlinkfilesetdevqa -J /filesystem/projectlinkfileset/dev
    mmlinkfileset filesys projectlinkfilesetdevqa -J /filesystem/projectlinkfileset/qa

    Now we can apply policies to a single fileset that applies to two directories. This is very much a nice to have but otherwise why have a separate link command if you can't use it more than once :-)

  • Guest
    Reply
    |     Jun 28, 2019

    So step by step.

    Basic scenario:
    File system /filesystem; Device: filesys
    User does: mkdir /filesystem/projectlinkfileset

    Later administrator does:
    mmcrfileset projectlinkfileset
    mmlinkfileset filesys projectlinkfileset -J /filesystem/projectlinkfileset

    Now we can apply policies to the directory. The current process requires:

    mv /filesystem/projectlinkfileset /filesystem/projectlinkfileset-bkup
    mmcrfileset projectlinkfileset
    mmlinkfileset filesys projectlinkfileset -J /filesystem/projectlinkfileset
    mv /filesystem/projectlinkfileset-bkup/* /filesystem/projectlinkfileset
    rm /filesystem/projectlinkfileset-bkup

    That may seem small but in a large, 24*7*366 operational system it can be hard to have the directory temporarily disappear or for it to be suddenly empty. Automated scripts break, etc.

    The current rules mean that you don't actually need separate create fileset and link fileset steps. You could the create and link in one step. So it would appear that the current rules were introduced due to an unforeseen restriction. So the question becomes what was that restriction and does it still exist. Which led me to the following alternate scenario:

    More capable scenario but this would also break the rule that a fileset can only be linked to a single file system object:

    User does:
    mkdir /filesystem/projectlinkfileset
    mkdir /filesystem/projectlinkfileset/dev
    mkdir /filesystem/projectlinkfileset/qa
    mkdir /filesystem/projectlinkfileset/release

    Later administrator does:
    mmcrfileset projectlinkfilesetdevqa
    mmlinkfileset filesys projectlinkfilesetdevqa -J /filesystem/projectlinkfileset/dev
    mmlinkfileset filesys projectlinkfilesetdevqa -J /filesystem/projectlinkfileset/qa

    Now we can apply policies to a single fileset that applies to two directories. This is very much a nice to have but otherwise why have a separate link command if you can't use it more than once :-)

  • Guest
    Reply
    |     Jun 28, 2019

    So step by step.

    Basic scenario:
    File system /filesystem; Device: filesys
    User does: mkdir /filesystem/projectlinkfileset

    Later administrator does:
    mmcrfileset projectlinkfileset
    mmlinkfileset filesys projectlinkfileset -J /filesystem/projectlinkfileset

    Now we can apply policies to the directory. The current process requires:

    mv /filesystem/projectlinkfileset /filesystem/projectlinkfileset-bkup
    mmcrfileset projectlinkfileset
    mmlinkfileset filesys projectlinkfileset -J /filesystem/projectlinkfileset
    mv /filesystem/projectlinkfileset-bkup/* /filesystem/projectlinkfileset
    rm /filesystem/projectlinkfileset-bkup

    That may seem small but in a large, 24*7*366 operational system it can be hard to have the directory temporarily disappear or for it to be suddenly empty. Automated scripts break, etc.

    The current rules mean that you don't actually need separate create fileset and link fileset steps. You could the create and link in one step. So it would appear that the current rules were introduced due to an unforeseen restriction. So the question becomes what was that restriction and does it still exist. Which led me to the following alternate scenario:

    More capable scenario but this would also break the rule that a fileset can only be linked to a single file system object:

    User does:
    mkdir /filesystem/projectlinkfileset
    mkdir /filesystem/projectlinkfileset/dev
    mkdir /filesystem/projectlinkfileset/qa
    mkdir /filesystem/projectlinkfileset/release

    Later administrator does:
    mmcrfileset projectlinkfilesetdevqa
    mmlinkfileset filesys projectlinkfilesetdevqa -J /filesystem/projectlinkfileset/dev
    mmlinkfileset filesys projectlinkfilesetdevqa -J /filesystem/projectlinkfileset/qa

    Now we can apply policies to a single fileset that applies to two directories. This is very much a nice to have but otherwise why have a separate link command if you can't use it more than once :-)

  • Guest
    Reply
    |     Jun 28, 2019

    So step by step.

    Basic scenario:
    File system /filesystem; Device: filesys
    User does: mkdir /filesystem/projectlinkfileset

    Later administrator does:
    mmcrfileset projectlinkfileset
    mmlinkfileset filesys projectlinkfileset -J /filesystem/projectlinkfileset

    Now we can apply policies to the directory. The current process requires:

    mv /filesystem/projectlinkfileset /filesystem/projectlinkfileset-bkup
    mmcrfileset projectlinkfileset
    mmlinkfileset filesys projectlinkfileset -J /filesystem/projectlinkfileset
    mv /filesystem/projectlinkfileset-bkup/* /filesystem/projectlinkfileset
    rm /filesystem/projectlinkfileset-bkup

    That may seem small but in a large, 24*7*366 operational system it can be hard to have the directory temporarily disappear or for it to be suddenly empty. Automated scripts break, etc.

    The current rules mean that you don't actually need separate create fileset and link fileset steps. You could the create and link in one step. So it would appear that the current rules were introduced due to an unforeseen restriction. So the question becomes what was that restriction and does it still exist. Which led me to the following alternate scenario:

    More capable scenario but this would also break the rule that a fileset can only be linked to a single file system object:

    User does:
    mkdir /filesystem/projectlinkfileset
    mkdir /filesystem/projectlinkfileset/dev
    mkdir /filesystem/projectlinkfileset/qa
    mkdir /filesystem/projectlinkfileset/release

    Later administrator does:
    mmcrfileset projectlinkfilesetdevqa
    mmlinkfileset filesys projectlinkfilesetdevqa -J /filesystem/projectlinkfileset/dev
    mmlinkfileset filesys projectlinkfilesetdevqa -J /filesystem/projectlinkfileset/qa

    Now we can apply policies to a single fileset that applies to two directories. This is very much a nice to have but otherwise why have a separate link command if you can't use it more than once :-)

  • Guest
    Reply
    |     Jun 28, 2019

    Can this be automated with the new watch folder capability? If not, can you provide a more detailed step by step description? We think we understand the general concept but not the exact requirement. (A phone call might be the best way to clarify, if you are available)

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.