<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:32:12 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-3243] sanity.sh test_77i: algo set to crc32 instead of adler</title>
                <link>https://jira.whamcloud.com/browse/LU-3243</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;I&apos;ve just seen this test failure:&lt;/p&gt;

&lt;p&gt;&apos;algo set to crc32 instead of adler&apos; &lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://maloo.whamcloud.com/test_sets/eae87668-aee2-11e2-a8d0-52540035b04c&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://maloo.whamcloud.com/test_sets/eae87668-aee2-11e2-a8d0-52540035b04c&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;against my patch:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://review.whamcloud.com/#change,3440&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/#change,3440&lt;/a&gt;&lt;/p&gt;</description>
                <environment></environment>
        <key id="18620">LU-3243</key>
            <summary>sanity.sh test_77i: algo set to crc32 instead of adler</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="1">Fixed</resolution>
                                        <assignee username="wc-triage">WC Triage</assignee>
                                    <reporter username="rhenwood">Richard Henwood</reporter>
                        <labels>
                    </labels>
                <created>Mon, 29 Apr 2013 18:04:46 +0000</created>
                <updated>Wed, 16 Jul 2014 14:33:03 +0000</updated>
                            <resolved>Fri, 13 Sep 2013 00:02:02 +0000</resolved>
                                                    <fixVersion>Lustre 2.4.1</fixVersion>
                    <fixVersion>Lustre 2.5.0</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                            <comments>
                            <comment id="57273" author="adilger" created="Mon, 29 Apr 2013 21:59:05 +0000"  >&lt;p&gt;Richard,&lt;br/&gt;
what CPU is being used in this testing?  The output from /proc/cpuinfo would be useful.&lt;/p&gt;

&lt;p&gt;If there are CPUs that support the PCLMULQDQ instruction on both client and OSS, and the checksums are at least 2x faster using crc32 than adler, it makes sense to choose the crc32 checksum by default.&lt;/p&gt;

&lt;p&gt;IMHO, the test seems a bit broken in that it is expecting adler, when in fact crc32 has always been a supported algorithm.  I guess the test was written this way because adler was hard-coded as the default (since it was always faster than crc32 in software) and has been around sufficiently long to be supported in all releases.  However, the client is still at liberty to choose crc32 if it is faster...&lt;/p&gt;

&lt;p&gt;I also noticed in test_77c that there is an error being printed:&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;error: set_param: writing to file /proc/fs/lustre/osc/lustre-OST0000-osc-ffff88007b2f9800/checksum_type: Invalid argument
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;but is lacking information for the user about why it is failing (the test itself is trying to set the checksum type to crc32 at this point).  I submitted &lt;a href=&quot;http://review.whamcloud.com/6205&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/6205&lt;/a&gt; to improve the error message, but that is not fixing the bug here.&lt;/p&gt;</comment>
                            <comment id="66557" author="pjones" created="Fri, 13 Sep 2013 00:02:02 +0000"  >&lt;p&gt;Landed for 2.4.1 and 2.5.0&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="25613">LU-5361</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|hzvpaf:</customfieldvalue>

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