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 Not under consideration
Created by Guest
Created on Mar 5, 2021

Command to check compressed usage size for each fileset quickly

We are performing IBM Spectrum Scale compression on each fileset on daily basis through gpfs policies. The df command is not showing the accurate usage for each fileset and only du shows the actual usage. But since du usually takes long time to provide results compare to df command, we need to get a gpfs command that can show the actual used size for each fileset quickly (like df). We checked with IBM support through the case TS005116351 and found there is no command that shows the required output right now and only mmdf command is available which does not show the fileset usage currently. Can we please create a new command or functionality to quickly get the used size of each fileset (like df command time)?

Idea priority High
  • Guest
    Reply
    |
    Sep 27, 2021

    Thank you for submitting this Spectrum Scale enhancement request. We are closing this request due to lack of additional information provided. Please open a new request if this feature is still needed.

  • Guest
    Reply
    |
    Jun 25, 2021

    Do you have quotas enabled ?
    If you have enabled quotas and then set the file system for --filesetdf (can be set dynamically with mmchfs) then you can get the usage data immediately by invoking the df command from a directory in the given fileset.


    If quotas not enabled , It may be possible to speed this up, but it is unlikely we will ever get to the near-instantaneous speed of df itself. Would you be satisfied with a command that runs (for example) 5x faster than the current mmlsfilesest? <----would like your feedback on this

  • Guest
    Reply
    |
    May 7, 2021

    It may be possible to speed this up, but it is unlikely we will ever get to the near-instantaneous speed of df itself. Would you be satisfied a command that runs (for example) 5x faster than than the current mmlsfilesest -d?

  • Guest
    Reply
    |
    Mar 15, 2021

    we do support this light weight method by enabling the --filesetdf option. However, without quota's enablement, we would only show the fileset inode space level inode usage(the block usage is still at file system wide). However, enabling quota for --filesetdf, which could affect the performance of data blocks allocation&deallocation, if users indeed doesn't need quota.

    So we should check with customers whether they're using quota or not, if using, then they can enable --filesetdf to get the fileset level space usage. If they only cares about the inodes usage, then simply enable --filesetdf should be good enough with 5.1.1 version.

  • Guest
    Reply
    |
    Mar 5, 2021

    This would be a useful feature to show in the GUI so that at a glance you can see the real vs compressed capacity on a per file set level... in the same way that the block storage arrays show the difference between real vs compressed capacity