<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:20: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-1911] Test failure on test suite sanity, subtest test_130a</title>
                <link>https://jira.whamcloud.com/browse/LU-1911</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;This issue was created by maloo for Johann &amp;lt;johann@whamcloud.com&amp;gt;&lt;/p&gt;

&lt;p&gt;This issue relates to the following test suite run: &lt;a href=&quot;https://maloo.whamcloud.com/test_sets/373e0ae6-fce6-11e1-a961-52540035b04c&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://maloo.whamcloud.com/test_sets/373e0ae6-fce6-11e1-a961-52540035b04c&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The sub-test test_130a failed with the following error:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;FIEMAP on 1-stripe file(/mnt/lustre/f.sanity.130a) failed;&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Info required for matching: sanity 130a&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;hm, it seems that all fiemap tests are failing on master ...
[12/09/12 17:28:11] Johann Lombardi: it seems to be due to an unexpected output format of filefrag
[12/09/12 17:28:32] Johann Lombardi: adilger: did we upgrade e2fsprogs recently?
[12/09/12 17:29:23] Johann Lombardi: Ian is telling me that it is the case
[12/09/12 17:29:50] Johann Lombardi: chris: could we revert to the previous version of e2fsprogs until this is fixed?
[12/09/12 17:30:01] Ian Colle: http://git.whamcloud.com/?p=tools/e2fsprogs.git;a=summary
[12/09/12 17:31:47] Ian Colle: Strange - summary page says it was last changed 5 hours ago, but I don&apos;t see anything in the summary from last night
[12/09/12 17:32:43] Johann Lombardi: http://git.whamcloud.com/?p=tools/e2fsprogs.git;a=shortlog;h=refs/heads/master-lustre
[12/09/12 17:32:55] Ian Colle: ahhh
[12/09/12 17:37:24] Johann Lombardi: output format was changed in one of Andreas&apos; patch it seems:
[12/09/12 17:37:35] Johann Lombardi: http://git.whamcloud.com/?p=tools/e2fsprogs.git;a=blobdiff;f=misc/filefrag.c;h=cddb422cd9ee81f330e85ecd810296e7db4b5ac8;hp=56985a1b0f2fe2cd83c808c3562c7197fed5c62d;hb=439cc86d17de637fff93f03580aff7c683f295ac;hpb=ba0318dfc17b037982639c561fe6038881c0266e
[12/09/12 17:38:40] Johann Lombardi: it used to be:
 ext:     device_logical:        physical_offset: length:  dev: flags:
   0:        0..      63:   33691548..  33691611:     64: 0005: network,eof

It is now:
 ext  logical   physical   expected length flags
   0:        0..      63:   33692596..  33692659:     64: 0002: network,eof

Somehow, it seems to confuse our fiemap tests ...
[12/09/12 17:40:35] Johann Lombardi: ah, the tests expect the &apos;:&apos; after column titles :(
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</description>
                <environment></environment>
        <key id="15910">LU-1911</key>
            <summary>Test failure on test suite sanity, subtest test_130a</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="1" iconUrl="https://jira.whamcloud.com/images/icons/priorities/blocker.svg">Blocker</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="1">Fixed</resolution>
                                        <assignee username="johann">Johann Lombardi</assignee>
                                    <reporter username="maloo">Maloo</reporter>
                        <labels>
                    </labels>
                <created>Wed, 12 Sep 2012 11:52:42 +0000</created>
                <updated>Tue, 18 Dec 2012 02:51:57 +0000</updated>
                            <resolved>Fri, 14 Sep 2012 19:12:09 +0000</resolved>
                                    <version>Lustre 2.3.0</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                            <comments>
                            <comment id="44695" author="johann" created="Wed, 12 Sep 2012 11:57:07 +0000"  >&lt;p&gt;Tentative patch:&lt;br/&gt;
&lt;a href=&quot;http://review.whamcloud.com/3956&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/3956&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="44702" author="adilger" created="Wed, 12 Sep 2012 13:40:18 +0000"  >&lt;p&gt;This is an error during merge on my part.  The lack of change to the header line is a mistake, because there is no &quot;expected&quot; column in the output either.  I&apos;ll fix this in e2fsprogs again. &lt;/p&gt;

&lt;p&gt;However, it is good to be lenient in what is accepted by the test, so I&apos;m not against the patch you submitted.   That said, the breakage should also be fixed in e2fsprogs or it will cause problems on every other branch as well. &lt;/p&gt;</comment>
                            <comment id="44709" author="pjones" created="Wed, 12 Sep 2012 15:00:25 +0000"  >&lt;p&gt;This is causing a lot of failures. Is is better to deal with it centrally to avoid having to make changes to every branch? Otherwise will we have all kinds of interop failures?&lt;/p&gt;</comment>
                            <comment id="44719" author="green" created="Wed, 12 Sep 2012 18:45:04 +0000"  >&lt;p&gt;I vote for reverting to older e2fsprogs version until newer one is in place. This avoids needs to rebases and will have an immediate positive impact.&lt;/p&gt;</comment>
                            <comment id="44720" author="ian" created="Wed, 12 Sep 2012 18:55:01 +0000"  >&lt;p&gt;I thought Chris had done just that while we worked Johann&apos;s patch in parallel.&lt;/p&gt;</comment>
                            <comment id="44732" author="pjones" created="Wed, 12 Sep 2012 21:54:05 +0000"  >&lt;p&gt;Well everything still seems to be failing with this error...&lt;/p&gt;</comment>
                            <comment id="44764" author="adilger" created="Thu, 13 Sep 2012 03:55:22 +0000"  >&lt;p&gt;Chris reverted to the earlier e2fsprogs-1.42.3.wc3 at 12:30 MT, but it may be that any tests already running had the old e2fsprogs installed.&lt;/p&gt;

&lt;p&gt;I&apos;ve since pushed an updated version of e2fsprogs-1.42.5.wc2 that should resolve the problem, but the e2fsprogs builds need to be re-enabled in order to test this out.&lt;/p&gt;

&lt;p&gt;Coincidentally, I found a much more serious defect in the filefrag/FIEMAP handling in Lustre, &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-1923&quot; title=&quot;filefrag with large fiemap buffer crashes client&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-1923&quot;&gt;&lt;del&gt;LU-1923&lt;/del&gt;&lt;/a&gt;, for which I&apos;ve submitted a separate lustre patch.&lt;/p&gt;</comment>
                            <comment id="44908" author="pjones" created="Fri, 14 Sep 2012 19:12:09 +0000"  >&lt;p&gt;This will not occur in the next upgrade to e2fsprogs&lt;/p&gt;</comment>
                            <comment id="44952" author="adilger" created="Sat, 15 Sep 2012 15:39:05 +0000"  >&lt;p&gt;Unfortunately, there was another instance of filefrag causing intermittent (but relatively frequent) errors, when being run on a file that was just written.  A fix has been pushed as e2fsprogs-1.42.5.wc3, and should be seen on new tests that are starting with this version.&lt;/p&gt;</comment>
                            <comment id="44953" author="adilger" created="Sat, 15 Sep 2012 15:40:08 +0000"  >&lt;p&gt;Link to TT-881, since that will allow proper e2fsprogs + Lustre testing before it affects all test runs.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="16067">LU-2004</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                                        </outwardlinks>
                                                        </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|hzv4b3:</customfieldvalue>

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