<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:35:34 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-3631] file stats are slow on filesystem start up</title>
                <link>https://jira.whamcloud.com/browse/LU-3631</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;NOAA had a question about an observed behavior. As part of their change management validation, they rerun a battery of tests after they make a change. One of those is mdtest. What has been observed is that after a downtime, the file stat performance is terrible. Like 400/s. After a while, it goes up to around 10-15k. It seems to be a function of load as opposed to time. The more the filesystem is used (due to other testing), the faster the stat performance increases.&lt;/p&gt;

&lt;p&gt;Are there any thoughts on why this might happen? I have tried preloading the OST metadata, but that didn&apos;t seem to have any effect. I thought that IB routing might be an issue, but even when the IB fabric is untouched, we see this issue. It seems like it must be a cache issue, but I am unsure what caches are being warmed up. Any insight on why we are seeing this and how to preload the cache would be great.&lt;/p&gt;

&lt;p&gt;Thanks.&lt;/p&gt;</description>
                <environment></environment>
        <key id="19985">LU-3631</key>
            <summary>file stats are slow on filesystem start up</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="5" iconUrl="https://jira.whamcloud.com/images/icons/priorities/trivial.svg">Trivial</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="6">Not a Bug</resolution>
                                        <assignee username="green">Oleg Drokin</assignee>
                                    <reporter username="kitwestneat">Kit Westneat</reporter>
                        <labels>
                    </labels>
                <created>Wed, 24 Jul 2013 23:40:07 +0000</created>
                <updated>Mon, 30 Apr 2018 17:41:07 +0000</updated>
                            <resolved>Wed, 2 Apr 2014 11:49:43 +0000</resolved>
                                    <version>Lustre 1.8.9</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                            <comments>
                            <comment id="62956" author="pjones" created="Thu, 25 Jul 2013 02:23:56 +0000"  >&lt;p&gt;Oleg&lt;/p&gt;

&lt;p&gt;What do you recommend?&lt;/p&gt;

&lt;p&gt;Peter&lt;/p&gt;</comment>
                            <comment id="63109" author="adilger" created="Mon, 29 Jul 2013 06:31:49 +0000"  >&lt;p&gt;This is a fairly typical scenario as the filesystem cache is warmed up after a restart. In particular, the inode bitmaps need to be read from disk.  If there are partially allocated itable blocks are also read from disk at allocation time (unallocated blocks are not read from disk).&lt;/p&gt;

&lt;p&gt;The inode bitmaps can be prefetched at boot time by running:&lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;dumpe2fs /dev/mdsdev 2&amp;gt; /dev/null
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;The problem of loading the inode bitmaps at startup time is avoided with Lustre 2.x formatted filesystems by using the flexbg feature. &lt;/p&gt;</comment>
                            <comment id="63174" author="kitwestneat" created="Mon, 29 Jul 2013 17:48:08 +0000"  >&lt;p&gt;Ok great, thanks!&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="52042">LU-10967</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|hzvw3j:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9351</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>