<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:37:46 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-3886] sanity test_56a: @@@@@@ FAIL: /usr/bin/lfs getstripe --obd wrong: found 6, expected 3</title>
                <link>https://jira.whamcloud.com/browse/LU-3886</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;This problem is similar with &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-3846&quot; title=&quot;Sanity 56u error with two OSTs&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-3846&quot;&gt;&lt;del&gt;LU-3846&lt;/del&gt;&lt;/a&gt; and &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-3858&quot; title=&quot;sanity test_27A: @@@@@@ FAIL: stripe count -1 != 1&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-3858&quot;&gt;&lt;del&gt;LU-3858&lt;/del&gt;&lt;/a&gt;. The test suit should wait for a few seconds after it clear the stripe of the directory. Otherwise, the newly created entries under the directory will have 2 stripe counts rather than 1.&lt;/p&gt;</description>
                <environment></environment>
        <key id="20786">LU-3886</key>
            <summary>sanity test_56a: @@@@@@ FAIL: /usr/bin/lfs getstripe --obd wrong: found 6, expected 3</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="3" iconUrl="https://jira.whamcloud.com/images/icons/priorities/major.svg">Major</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="5">Cannot Reproduce</resolution>
                                        <assignee username="emoly.liu">Emoly Liu</assignee>
                                    <reporter username="lixi">Li Xi</reporter>
                        <labels>
                    </labels>
                <created>Thu, 5 Sep 2013 10:51:04 +0000</created>
                <updated>Tue, 17 Mar 2020 03:24:41 +0000</updated>
                            <resolved>Tue, 17 Mar 2020 03:24:41 +0000</resolved>
                                    <version>Lustre 2.5.0</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                            <comments>
                            <comment id="65901" author="pjones" created="Fri, 6 Sep 2013 03:37:50 +0000"  >&lt;p&gt;Emoly&lt;/p&gt;

&lt;p&gt;Could you please comment on this one?&lt;/p&gt;

&lt;p&gt;Thanks&lt;/p&gt;

&lt;p&gt;Peter&lt;/p&gt;</comment>
                            <comment id="66064" author="emoly.liu" created="Mon, 9 Sep 2013 15:36:36 +0000"  >&lt;p&gt;&quot;lfs setstripe -d&quot; should be enough to clear directory striping information. LiXi, could you tell me how you hit this problem? &lt;/p&gt;

&lt;p&gt;IMO, we can add &quot;lfs getstripe -v&quot; after &quot;setstripe -d&quot; to print that striping information, and see if this problem will happen again.&lt;/p&gt;</comment>
                            <comment id="66143" author="lixi" created="Tue, 10 Sep 2013 00:58:09 +0000"  >&lt;p&gt;I&apos;ve post the script (run-sanity.sh) to hit this problem (and &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-3858&quot; title=&quot;sanity test_27A: @@@@@@ FAIL: stripe count -1 != 1&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-3858&quot;&gt;&lt;del&gt;LU-3858&lt;/del&gt;&lt;/a&gt;, &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-3846&quot; title=&quot;Sanity 56u error with two OSTs&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-3846&quot;&gt;&lt;del&gt;LU-3846&lt;/del&gt;&lt;/a&gt;). It will hit the problem every time it runs.&lt;/p&gt;</comment>
                            <comment id="66145" author="lixi" created="Tue, 10 Sep 2013 01:08:46 +0000"  >&lt;p&gt;What is interesting is that when I add a sleep into the test suit, the problem is gone. That makes me believe that the problem is similar with &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-3858&quot; title=&quot;sanity test_27A: @@@@@@ FAIL: stripe count -1 != 1&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-3858&quot;&gt;&lt;del&gt;LU-3858&lt;/del&gt;&lt;/a&gt;. Emoly, would you please check the attachment of &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-3858&quot; title=&quot;sanity test_27A: @@@@@@ FAIL: stripe count -1 != 1&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-3858&quot;&gt;&lt;del&gt;LU-3858&lt;/del&gt;&lt;/a&gt; first? I.e. &lt;a href=&quot;https://jira.hpdd.intel.com/secure/attachment/13414/run.sh&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://jira.hpdd.intel.com/secure/attachment/13414/run.sh&lt;/a&gt;. It shows that the effect of default stripe is delayed. Thanks!&lt;/p&gt;

&lt;p&gt;test_56a() {    # was test_56&lt;br/&gt;
        rm -rf $DIR/$tdir&lt;br/&gt;
        $SETSTRIPE -d $DIR&lt;br/&gt;
        test_mkdir -p $DIR/$tdir/dir&lt;br/&gt;
        NUMFILES=3&lt;br/&gt;
        NUMFILESx2=$(($NUMFILES * 2))&lt;br/&gt;
        sleep 10 # This will fix the problem.&lt;br/&gt;
        for i in `seq 1 $NUMFILES` ; do&lt;br/&gt;
                touch $DIR/$tdir/file$i&lt;br/&gt;
                touch $DIR/$tdir/dir/file$i&lt;br/&gt;
        done&lt;br/&gt;
......&lt;/p&gt;</comment>
                            <comment id="66162" author="emoly.liu" created="Tue, 10 Sep 2013 09:14:49 +0000"  >&lt;p&gt;I just ran the script of &quot;https://jira.hpdd.intel.com/secure/attachment/13414/run.sh&quot; on my local VM. It showed me 10000 times &quot;No errors after xxx iters&quot;.&lt;/p&gt;

&lt;p&gt;My step is:&lt;br/&gt;
1. mount lustre&lt;br/&gt;
2. mkdir /mnt/lustre/d&lt;br/&gt;
3. sh run.sh /mnt/lustre/d&lt;/p&gt;

&lt;p&gt;I tried several times, no error happened.&lt;/p&gt;</comment>
                            <comment id="66165" author="lixi" created="Tue, 10 Sep 2013 09:30:30 +0000"  >&lt;p&gt;Oh, sorry, plase run on lustre mount point &apos;/mnt/lustre&apos; rather than its directory &apos;/mnt/lustre/dir&apos;, i.e. sh run.sh /mnt/lustre/&lt;/p&gt;

&lt;p&gt;I got following output:&lt;/p&gt;

&lt;p&gt;No error after 640 iters&lt;br/&gt;
-1  != 1&lt;br/&gt;
Does not become correct after 0 seconds&lt;br/&gt;
Does not become correct after 1 seconds&lt;br/&gt;
Does not become correct after 2 seconds&lt;br/&gt;
Does not become correct after 3 seconds&lt;br/&gt;
Does not become correct after 4 seconds&lt;br/&gt;
Does not become correct after 5 seconds&lt;br/&gt;
Does not become correct after 6 seconds&lt;br/&gt;
Become correct after 7 seconds&lt;/p&gt;</comment>
                            <comment id="66184" author="emoly.liu" created="Tue, 10 Sep 2013 14:57:54 +0000"  >&lt;p&gt;Yes, this time I hit that. I will investigate it.&lt;/p&gt;</comment>
                            <comment id="66318" author="emoly.liu" created="Wed, 11 Sep 2013 07:21:12 +0000"  >&lt;p&gt;The problem you found by run.sh is probably related to the following code:&lt;/p&gt;

&lt;p&gt;When we set stripe for root(mount point), set_default is enabled in ll_dir_ioctl()&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;        &lt;span class=&quot;code-keyword&quot;&gt;case&lt;/span&gt; LL_IOC_LOV_SETSTRIPE: {
...
                &lt;span class=&quot;code-object&quot;&gt;int&lt;/span&gt; set_default = 0;
...
                &lt;span class=&quot;code-keyword&quot;&gt;if&lt;/span&gt; (inode-&amp;gt;i_sb-&amp;gt;s_root == file-&amp;gt;f_dentry)
                        set_default = 1;

                &lt;span class=&quot;code-comment&quot;&gt;/* in v1 and v3 cases lumv1 points to data */&lt;/span&gt;
                rc = ll_dir_setstripe(inode, lumv1, set_default);
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Then, in ll_dir_setstripe() if set_default=1, we will call ll_send_mgc_param() to set information asynchronously.&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;        &lt;span class=&quot;code-keyword&quot;&gt;if&lt;/span&gt; (set_default &amp;amp;&amp;amp; mgc-&amp;gt;u.cli.cl_mgc_mgsexp) {
                &lt;span class=&quot;code-comment&quot;&gt;/* Set root stripesize */&lt;/span&gt;
                &lt;span class=&quot;code-comment&quot;&gt;/* Set root stripecount */&lt;/span&gt;
                &lt;span class=&quot;code-comment&quot;&gt;/* Set root stripeoffset */&lt;/span&gt;
        }
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Since you run setstripe very frequently and many times in run.sh, the config log queue might be very long (bottleneck), and mgs will take more time to process it.&lt;/p&gt;

&lt;p&gt;BTW, can you hit this problem if you don&apos;t use run.sh, just run sanity.sh regularly?&lt;/p&gt;</comment>
                            <comment id="66321" author="lixi" created="Wed, 11 Sep 2013 07:58:27 +0000"  >&lt;p&gt;Yeah, I hit the problem of &apos;found 6, expected 3&apos; every time when I run sanity.sh. &lt;/p&gt;</comment>
                            <comment id="104644" author="jamesanunez" created="Sun, 25 Jan 2015 23:10:01 +0000"  >&lt;p&gt;I&apos;ve hit this problem with lustre-master tag 2.6.92. Results at &lt;a href=&quot;https://testing.hpdd.intel.com/test_sets/37e63f92-9f0d-11e4-91b3-5254006e85c2&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://testing.hpdd.intel.com/test_sets/37e63f92-9f0d-11e4-91b3-5254006e85c2&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="265389" author="adilger" created="Tue, 17 Mar 2020 03:24:41 +0000"  >&lt;p&gt;Haven&apos;t seen this in a long time.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="31826">LU-7071</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                        <issuelink>
            <issuekey id="20655">LU-3846</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="20707">LU-3858</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="13446" name="run-sanity.sh" size="264" author="lixi" created="Tue, 10 Sep 2013 00:58:09 +0000"/>
                    </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_10490" key="com.atlassian.jira.plugin.system.customfieldtypes:datepicker">
                        <customfieldname>End date</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Tue, 1 Sep 2015 10:51:04 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hzw073:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>10111</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>
                                                                                                                        <customfield id="customfield_10493" key="com.atlassian.jira.plugin.system.customfieldtypes:datepicker">
                        <customfieldname>Start date</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Thu, 5 Sep 2013 10:51:04 +0000</customfieldvalue>

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