<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:15:16 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-8172] match 1 length 172 too big: 160 left, 160 allowed</title>
                <link>https://jira.whamcloud.com/browse/LU-8172</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Trying to run simple lnet_selftest failed between 2 nodes with this error&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;00000400:00020000:13.0F:1463699033.377705:0:8764:0:(lib-ptl.c:190:lnet_try_match_md()) Matching packet from 12345-10.151.27.60@o2ib, match 1 length 172 too big: 160 left, 160 allowed
00000400:00000100:13.0:1463699033.420950:0:8764:0:(lib-move.c:1479:lnet_parse_put()) Dropping PUT from 12345-10.151.27.60@o2ib portal 51 match 1 offset 0 length 172: 4
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;It works within the same node.&lt;/p&gt;</description>
                <environment>2.7.1 with &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-3322&quot; title=&quot;ko2iblnd support for different map_on_demand and peer_credits between systems&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-3322&quot;&gt;&lt;strike&gt;LU-3322&lt;/strike&gt;&lt;/a&gt;</environment>
        <key id="37090">LU-8172</key>
            <summary>match 1 length 172 too big: 160 left, 160 allowed</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="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="6">Not a Bug</resolution>
                                        <assignee username="doug">Doug Oucharek</assignee>
                                    <reporter username="mhanafi">Mahmoud Hanafi</reporter>
                        <labels>
                    </labels>
                <created>Thu, 19 May 2016 23:16:17 +0000</created>
                <updated>Tue, 24 May 2016 21:55:37 +0000</updated>
                            <resolved>Tue, 24 May 2016 21:55:37 +0000</resolved>
                                    <version>Lustre 2.7.0</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                            <comments>
                            <comment id="152943" author="jaylan" created="Fri, 20 May 2016 01:13:01 +0000"  >&lt;p&gt;I rebased our nas-2.7.1-fe git repo with b2_7_fe on 5/12.&lt;br/&gt;
&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-3322&quot; title=&quot;ko2iblnd support for different map_on_demand and peer_credits between systems&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-3322&quot;&gt;&lt;del&gt;LU-3322&lt;/del&gt;&lt;/a&gt; was pulled in with that rebase. We did not have the problem before the rebase.&lt;/p&gt;

&lt;p&gt;There are some LU patches we carry not in b2_7_fe:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7808&quot; title=&quot;Service threads hung at ptlrpc_abort_bulk&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7808&quot;&gt;&lt;del&gt;LU-7808&lt;/del&gt;&lt;/a&gt; lnet: Debug patch to investigate MD Unlink&lt;br/&gt;
&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7733&quot; title=&quot;ptlrpc_lprocfs_svc_req_history_show (Seq_printf) time resolution should be higher than 1 second.&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7733&quot;&gt;&lt;del&gt;LU-7733&lt;/del&gt;&lt;/a&gt; ptlrpc: print times in microseconds&lt;br/&gt;
&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7795&quot; title=&quot;least_qunit should be tunnable&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7795&quot;&gt;&lt;del&gt;LU-7795&lt;/del&gt;&lt;/a&gt; quota: tuneable soft least qunit&lt;br/&gt;
&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-6433&quot; title=&quot;MDS deadlock in qouta  &quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-6433&quot;&gt;&lt;del&gt;LU-6433&lt;/del&gt;&lt;/a&gt; quota: handle QUOTA_DQACQ in READPAGE portal&lt;br/&gt;
&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7569&quot; title=&quot;IB leaf switch caused LNet routers to crash&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7569&quot;&gt;&lt;del&gt;LU-7569&lt;/del&gt;&lt;/a&gt; o2iblnd: avoid intensive reconnecting&lt;br/&gt;
&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7210&quot; title=&quot;ASSERTION( peer-&amp;gt;ibp_connecting == 0 )&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7210&quot;&gt;&lt;del&gt;LU-7210&lt;/del&gt;&lt;/a&gt; o2iblnd: take extra refcount in kiblnd_connreq_done&lt;br/&gt;
&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7054&quot; title=&quot;ib_cm scalling issue when lustre clients connect to OSS&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7054&quot;&gt;&lt;del&gt;LU-7054&lt;/del&gt;&lt;/a&gt; o2iblnd: less intense allocating retry&lt;br/&gt;
Revert &quot;&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7054&quot; title=&quot;ib_cm scalling issue when lustre clients connect to OSS&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7054&quot;&gt;&lt;del&gt;LU-7054&lt;/del&gt;&lt;/a&gt; o2iblnd: less intense allocating retry&quot;&lt;br/&gt;
&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7372&quot; title=&quot;replay-dual test_26: test failed to respond and timed out&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7372&quot;&gt;&lt;del&gt;LU-7372&lt;/del&gt;&lt;/a&gt; mgs: reprocess all locks at device fini&lt;br/&gt;
&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-5704&quot; title=&quot;lfs getstripe hangs on fifo files&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-5704&quot;&gt;&lt;del&gt;LU-5704&lt;/del&gt;&lt;/a&gt; utils: stop open hangs on fifo files&lt;br/&gt;
&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7054&quot; title=&quot;ib_cm scalling issue when lustre clients connect to OSS&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7054&quot;&gt;&lt;del&gt;LU-7054&lt;/del&gt;&lt;/a&gt; o2iblnd: less intense allocating retry&lt;br/&gt;
&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7506&quot; title=&quot;lfs quota -h should support petabytes output&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7506&quot;&gt;&lt;del&gt;LU-7506&lt;/del&gt;&lt;/a&gt; lfs: &quot;lfs quota -h&quot; should support petabytes output&lt;/p&gt;

&lt;p&gt;The git repo can be accessed at github. Peter Jones&apos;s account has access to it.&lt;br/&gt;
&lt;a href=&quot;https://github.com/NASAEarthExchange/lustre-nas-fe/commits/nas-2.7.1&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/NASAEarthExchange/lustre-nas-fe/commits/nas-2.7.1&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="152954" author="pjones" created="Fri, 20 May 2016 05:19:00 +0000"  >&lt;p&gt;Doug&lt;/p&gt;

&lt;p&gt;Could you please advise?&lt;/p&gt;

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

&lt;p&gt;Peter&lt;/p&gt;</comment>
                            <comment id="153043" author="doug" created="Fri, 20 May 2016 18:07:18 +0000"  >&lt;p&gt;Is the exact same build running on all the nodes involved in the self test?  My interpretation of the error is that the message size we are anticipating is 12 bytes less than the amount which was sent.  &lt;/p&gt;</comment>
                            <comment id="153095" author="mhanafi" created="Sat, 21 May 2016 00:18:19 +0000"  >&lt;p&gt;Are there any issue with running 2.7.1+&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-3322&quot; title=&quot;ko2iblnd support for different map_on_demand and peer_credits between systems&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-3322&quot;&gt;&lt;del&gt;LU-3322&lt;/del&gt;&lt;/a&gt; server and 2.5.3or2.7.1 none &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-3322&quot; title=&quot;ko2iblnd support for different map_on_demand and peer_credits between systems&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-3322&quot;&gt;&lt;del&gt;LU-3322&lt;/del&gt;&lt;/a&gt; clients?&lt;/p&gt;</comment>
                            <comment id="153103" author="mhanafi" created="Sat, 21 May 2016 01:33:26 +0000"  >&lt;p&gt;There is incompatibility of lst between lu-3322 builds and non lu-3322. This was the issue I was having&lt;/p&gt;

&lt;p&gt;Should lst work with a build without &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-3322&quot; title=&quot;ko2iblnd support for different map_on_demand and peer_credits between systems&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-3322&quot;&gt;&lt;del&gt;LU-3322&lt;/del&gt;&lt;/a&gt; and one with &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-3322&quot; title=&quot;ko2iblnd support for different map_on_demand and peer_credits between systems&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-3322&quot;&gt;&lt;del&gt;LU-3322&lt;/del&gt;&lt;/a&gt;? &lt;/p&gt;
</comment>
                            <comment id="153104" author="jaylan" created="Sat, 21 May 2016 01:34:26 +0000"  >&lt;p&gt;Mahmoud, our nas-2.7.1-4.1nasS server and nas-2.7.1-4nasC client both have &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-3322&quot; title=&quot;ko2iblnd support for different map_on_demand and peer_credits between systems&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-3322&quot;&gt;&lt;del&gt;LU-3322&lt;/del&gt;&lt;/a&gt;.&lt;br/&gt;
The nas-2.5.3 client does not have &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-3322&quot; title=&quot;ko2iblnd support for different map_on_demand and peer_credits between systems&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-3322&quot;&gt;&lt;del&gt;LU-3322&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="153115" author="mhanafi" created="Sat, 21 May 2016 02:58:56 +0000"  >&lt;p&gt;after trying out different version it looks like &quot;&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7808&quot; title=&quot;Service threads hung at ptlrpc_abort_bulk&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7808&quot;&gt;&lt;del&gt;LU-7808&lt;/del&gt;&lt;/a&gt; lnet: Debug patch to investigate MD Unlink&quot; is where it breaks.&lt;/p&gt;</comment>
                            <comment id="153120" author="pjones" created="Sat, 21 May 2016 14:24:53 +0000"  >&lt;p&gt;Mahmoud&lt;/p&gt;

&lt;p&gt;I recall that this patch was quite different between the two versions. Do you have the appropriate version on both releases? Does everything work fine if you remove it altogether? &lt;/p&gt;

&lt;p&gt;Peter&lt;/p&gt;</comment>
                            <comment id="153284" author="jaylan" created="Tue, 24 May 2016 00:33:20 +0000"  >&lt;p&gt;Peter,&lt;/p&gt;

&lt;p&gt;We have correct versions of the &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7808&quot; title=&quot;Service threads hung at ptlrpc_abort_bulk&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7808&quot;&gt;&lt;del&gt;LU-7808&lt;/del&gt;&lt;/a&gt; lnet debug patches.&lt;br/&gt;
The b2_5_fe(#19643, patch set 4) and b2_7_fe(#19916 patch set 1) are different.&lt;/p&gt;</comment>
                            <comment id="153359" author="doug" created="Tue, 24 May 2016 15:40:51 +0000"  >&lt;p&gt;The 3 new stats I added to the debug patch for &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7808&quot; title=&quot;Service threads hung at ptlrpc_abort_bulk&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7808&quot;&gt;&lt;del&gt;LU-7808&lt;/del&gt;&lt;/a&gt; add up to 12 bytes and are traded between the two nodes during an lnet-selftest.  So it looks like one side is sending the new 3 stats but the other side is not expecting them.  I checked the two patches and they both should be sending/receiving the new 3 stats.&lt;/p&gt;

&lt;p&gt;As well as LNet, the debug patches for &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7808&quot; title=&quot;Service threads hung at ptlrpc_abort_bulk&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7808&quot;&gt;&lt;del&gt;LU-7808&lt;/del&gt;&lt;/a&gt; changed the lnet-selftest module.  Has the updated lnet-selftest module been updated on both nodes?&lt;/p&gt;</comment>
                            <comment id="153401" author="mhanafi" created="Tue, 24 May 2016 20:17:19 +0000"  >&lt;p&gt;It does look like this was the main issue and lst didn&apos;t match across all sides.&lt;/p&gt;

&lt;p&gt;You can close this issue.&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|hzyc9z:</customfieldvalue>

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