<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:38:56 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Whamcloud Community JIRA</title>
    <link>https://jira.whamcloud.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.4.14</version>
        <build-number>940014</build-number>
        <build-date>05-12-2023</build-date>
    </build-info>


<item>
            <title>[LU-10873] Add support for used inode/space on MDT/OST proc</title>
                <link>https://jira.whamcloud.com/browse/LU-10873</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;We have a monitoring system which can get the informations from&lt;br/&gt;
the /proc entries of Lustre. However, the Lustre doesn&apos;t export the&lt;br/&gt;
used inode/space on MDT/OST, this patch adds used inode/space info&lt;br/&gt;
in osd/lod layer:&lt;/p&gt;

&lt;p&gt;/proc/fs/lustre/osd-*/testfs-OST0000/filesused&lt;br/&gt;
/proc/fs/lustre/lod/testfs-MDT0000-mdtlov/filesused&lt;/p&gt;

&lt;p&gt;/proc/fs/lustre/osd-*/testfs-OST0000/kbytesused&lt;br/&gt;
/proc/fs/lustre/lod/testfs-MDT0000-mdtlov/kbytesused&lt;/p&gt;</description>
                <environment></environment>
        <key id="51629">LU-10873</key>
            <summary>Add support for used inode/space on MDT/OST proc</summary>
                <type id="2" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11311&amp;avatarType=issuetype">New Feature</type>
                                            <priority id="4" iconUrl="https://jira.whamcloud.com/images/icons/priorities/minor.svg">Minor</priority>
                        <status id="6" iconUrl="https://jira.whamcloud.com/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="10200">Won&apos;t Do</resolution>
                                        <assignee username="qian">Qian Yingjin</assignee>
                                    <reporter username="qian">Qian Yingjin</reporter>
                        <labels>
                    </labels>
                <created>Tue, 3 Apr 2018 06:40:44 +0000</created>
                <updated>Mon, 30 Apr 2018 18:00:31 +0000</updated>
                            <resolved>Mon, 30 Apr 2018 18:00:31 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>6</watches>
                                                                            <comments>
                            <comment id="225002" author="gerrit" created="Tue, 3 Apr 2018 06:49:14 +0000"  >&lt;p&gt;Yingjin Qian (qian@ddn.com) uploaded a new patch: &lt;a href=&quot;https://review.whamcloud.com/31854&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/31854&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-10873&quot; title=&quot;Add support for used inode/space on MDT/OST proc&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-10873&quot;&gt;&lt;del&gt;LU-10873&lt;/del&gt;&lt;/a&gt; lustre: Add support for used inode/space on MDT/OST proc&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: afb9c30d283b9c420dd2c20690001d301cbe13bb&lt;/p&gt;</comment>
                            <comment id="225089" author="adilger" created="Wed, 4 Apr 2018 08:29:31 +0000"  >&lt;p&gt;The &lt;tt&gt;kbytesused&lt;/tt&gt; and &lt;tt&gt;inodesused&lt;/tt&gt; amounts are just &lt;tt&gt;kbytestotal - kbytesfree&lt;/tt&gt; and &lt;tt&gt;inodestotal - inodesfree&lt;/tt&gt;, so there is no need to export them separately.&lt;/p&gt;</comment>
                            <comment id="225963" author="lixi" created="Fri, 13 Apr 2018 07:36:26 +0000"  >&lt;p&gt;The used capacity/inode can be calculated indeed from total - free. However, mathematical operation is not supported in all monitoring solutions, at least not in the framework that we are currently using. We adding the support, but still, I think other users would still find that they can not get the used capacity/inode easily. And calculating it manually from total and free capacity/inode obviously is not a good experience for administrators.&lt;/p&gt;</comment>
                            <comment id="226962" author="lixi" created="Mon, 30 Apr 2018 18:00:03 +0000"  >&lt;p&gt;This patch is less essential for us (DDN) now, since we&apos;ve implemented the math support in our monitoring system just a few hours ago. I am going to abandon the patch and close this ticket. Maybe other users of Lustre might found it useful to be able to read used inode/space directly from /proc. If anyone feels necessary, just re-open this ticket.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                <customfield id="customfield_10890" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hzzv4f:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>