<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:15:01 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-1256] Question about checksums</title>
                <link>https://jira.whamcloud.com/browse/LU-1256</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;I have a few questions about Checksums.&lt;/p&gt;

&lt;p&gt;Section 19.5.1 of the manual says:&lt;/p&gt;

&lt;p&gt;  To check the status of a wire checksum, run:&lt;/p&gt;

&lt;p&gt;  lctl get_param osc.*.checksums&lt;/p&gt;

&lt;p&gt;Does that mean that clearing this parameter only clears the wire checksum?&lt;/p&gt;

&lt;p&gt;Does writing each file named  /proc/fs/lustre/osc/*/checksums do the same thing?&lt;/p&gt;

&lt;p&gt;Is there a way to permanently disable checksums?&lt;/p&gt;

&lt;p&gt;Thanks.&lt;/p&gt;
</description>
                <environment></environment>
        <key id="13695">LU-1256</key>
            <summary>Question about checksums</summary>
                <type id="4" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11310&amp;avatarType=issuetype">Improvement</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="cliffw">Cliff White</assignee>
                                    <reporter username="rspellman">Roger Spellman</reporter>
                        <labels>
                    </labels>
                <created>Fri, 23 Mar 2012 14:31:36 +0000</created>
                <updated>Tue, 17 Apr 2012 14:10:23 +0000</updated>
                            <resolved>Tue, 17 Apr 2012 14:10:23 +0000</resolved>
                                    <version>Lustre 2.1.0</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                            <comments>
                            <comment id="31992" author="pjones" created="Fri, 23 Mar 2012 16:04:48 +0000"  >&lt;p&gt;Cliff&lt;/p&gt;

&lt;p&gt;Could you please help out with this one?&lt;/p&gt;

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

&lt;p&gt;Peter&lt;/p&gt;</comment>
                            <comment id="31994" author="cliffw" created="Fri, 23 Mar 2012 16:53:51 +0000"  >&lt;p&gt;Are you using the current Lustre manual? I am checking the 2.0 manual, per 19.5.1. &lt;br/&gt;
Does seem to be a bit unclear, perhaps should be rewritten. &lt;/p&gt;

&lt;p&gt;First, in general, the old way of parameter access is directly to the /proc files, the new&lt;br/&gt;
modern way is using get/set commands, if the path is the same both (atm) should do the same thing, but the get/set method&lt;br/&gt;
is future-compatible. You should be able to set a persistent value with lctl conf_param.&lt;/p&gt;

&lt;p&gt;Both types of checksums are controlled by &quot;lctl set_param llite.*.checksum_pages&quot; which is a client-only parameter. &lt;/p&gt;

&lt;p&gt;Network (wire) checksums can be set/unset with the osc.*.checksums parameter. This is done per-client and per ost connection.&lt;br/&gt;
Again, you can set/get with lctl or by direct file access. &lt;/p&gt;

&lt;p&gt;So, you can have network and memory checksums, or memory only, or none. &lt;/p&gt;</comment>
                            <comment id="32116" author="rspellman" created="Mon, 26 Mar 2012 09:45:27 +0000"  >&lt;p&gt;Thanks, Cliff.&lt;/p&gt;

&lt;p&gt;Is there a way to permanently disable checksums?&lt;/p&gt;

&lt;p&gt;There is CRC on the wire, and ECC on the RAM.&lt;br/&gt;
Exactly what errors are the checksums supposed to catch?  &lt;/p&gt;</comment>
                            <comment id="33358" author="cliffw" created="Tue, 3 Apr 2012 11:06:03 +0000"  >&lt;p&gt;As I said, you should be able to turn them off persistently with lctl conf_param, there is no other switch.  CRC and ECC are hardware checksums, the Lustre checksums include the Lustre stack and are supposed to catch any issues in that area. &lt;/p&gt;</comment>
                            <comment id="34950" author="pjones" created="Tue, 17 Apr 2012 14:10:23 +0000"  >&lt;p&gt;As per Peter Piela this ticket can be closed&lt;/p&gt;</comment>
                    </comments>
                    <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|hzw02n:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>10091</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>