<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:32:41 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-3296] fs/lustre/mdt/*/md_stats not showing any stats after remount</title>
                <link>https://jira.whamcloud.com/browse/LU-3296</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;I noticed that the md_stats proc file was empty, although there was activity on the filesystem and exports/*/stats contained several stats and were being updated. &lt;/p&gt;

&lt;p&gt;I unmounted and remounted the fs, no change. &lt;/p&gt;

&lt;p&gt;I rebooted, and md_stats contained usual operation stats data. &lt;/p&gt;

&lt;p&gt;Then remounted the mdt, and md_stats stayed empty again.&lt;/p&gt;

&lt;p&gt;Also,  fs/lustre/mdt/*/stats is empty, and remained empty after a reboot and remounts. &lt;/p&gt;

&lt;p&gt;My normal procedure for creating a lustre target does do a remount after the initial registration step, so it&apos;s possible this only occurs after remounting the mdt. &lt;/p&gt;
</description>
                <environment></environment>
        <key id="18753">LU-3296</key>
            <summary>fs/lustre/mdt/*/md_stats not showing any stats after remount</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="4" iconUrl="https://jira.whamcloud.com/images/icons/priorities/minor.svg">Minor</priority>
                        <status id="5" iconUrl="https://jira.whamcloud.com/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="3">Duplicate</resolution>
                                        <assignee username="wc-triage">WC Triage</assignee>
                                    <reporter username="rread">Robert Read</reporter>
                        <labels>
                    </labels>
                <created>Wed, 8 May 2013 17:39:20 +0000</created>
                <updated>Fri, 10 May 2013 23:05:23 +0000</updated>
                            <resolved>Thu, 9 May 2013 07:26:23 +0000</resolved>
                                    <version>Lustre 2.4.0</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                            <comments>
                            <comment id="57991" author="di.wang" created="Thu, 9 May 2013 07:25:49 +0000"  >&lt;p&gt;after some investigation, I think this is the same problem as &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-2979&quot; title=&quot;sanity 133a: proc counter for mkdir on mds1 was not incremented&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-2979&quot;&gt;&lt;del&gt;LU-2979&lt;/del&gt;&lt;/a&gt;. so I will close this one and try to fix there.&lt;/p&gt;</comment>
                            <comment id="57992" author="di.wang" created="Thu, 9 May 2013 07:26:23 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-2979&quot; title=&quot;sanity 133a: proc counter for mkdir on mds1 was not incremented&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-2979&quot;&gt;&lt;del&gt;LU-2979&lt;/del&gt;&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="58056" author="keith" created="Thu, 9 May 2013 19:25:14 +0000"  >&lt;p&gt;I wonder if this could be related to  &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-2902&quot; title=&quot;sanity test_156: NOT IN CACHE: before: , after: &quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-2902&quot;&gt;&lt;del&gt;LU-2902&lt;/del&gt;&lt;/a&gt; sanity test_156: NOT IN CACHE: before: , after:  &lt;br/&gt;
We are finding that in some cases some /proc entries are just not present for some still unknown reason. &lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                            <outwardlinks description="duplicates">
                                        <issuelink>
            <issuekey id="17986">LU-2979</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="18760">LU-3300</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <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|hzvqfz:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>8162</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10060" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Severity</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10022"><![CDATA[3]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>