<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:01:27 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-6582] Wireshark fails to parse LDLM_ENQUEUE RPC - likely for layout lock</title>
                <link>https://jira.whamcloud.com/browse/LU-6582</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;It looks to me like there is a least one bug in the Wireshark parsing. What I see is an LDLM_ENQUEUE that I &lt;em&gt;think&lt;/em&gt; is wanting to do RQF_LDLM_INTENT_GETXATTR in order to establish a layout lock on the MDT. Some of the structures/fields appear to be missing in the parsed output,&lt;br/&gt;
the LDLM_ENQUEUE request appears in the output with &#179;LustreBUG&#178; in place&lt;br/&gt;
of &#179;LUSTRE&#178;, and the LDLM_ENQUEUE reply says &#179;malformed packet&#178;. &lt;/p&gt;

&lt;p&gt;A simple experiment that will replicate this behavior is to run the shell command &apos;touch -c file&apos;. I do it from a client that has not previously visited the file or directory, so I know that nothing is cached. I also have the file precreated from a separate client, so that there really is a file to &apos;touch&apos;. The &apos;-c&apos; suppresses any file create/file open that otherwise might be attempted, so you just get the simple &apos;setattr&apos; behaviour. After the resulting MDS_REINT:REINT_SETATTR RPCs are exchanged, and before the subsequent MDS_GETXATTR:trusted.lov that get the actual layout, there is an LDLM_ENQUEUE exchanged that exhibits the problem. It&apos;s a good guess that it is trying to get a layout lock. The actual activities appear to be working fine, it is just the Wireshark parsing that appears to be a problem.&lt;/p&gt;</description>
                <environment></environment>
        <key id="29983">LU-6582</key>
            <summary>Wireshark fails to parse LDLM_ENQUEUE RPC - likely for layout lock</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="utopiabound">Nathaniel Clark</assignee>
                                    <reporter username="uselton">Andrew Uselton</reporter>
                        <labels>
                            <label>wireshark</label>
                    </labels>
                <created>Thu, 7 May 2015 18:22:41 +0000</created>
                <updated>Sat, 3 Jun 2017 04:45:05 +0000</updated>
                            <resolved>Sat, 3 Jun 2017 04:45:05 +0000</resolved>
                                                    <fixVersion>Lustre 2.10.0</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                            <comments>
                            <comment id="114643" author="utopiabound" created="Thu, 7 May 2015 20:01:57 +0000"  >&lt;p&gt;Reproduction:&lt;br/&gt;
On client 1&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;echo &amp;gt; /lustre/path/to/file1
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Wireshark dump of following transaction:&lt;/p&gt;

&lt;p&gt;On client 2&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;touch -c /lustre/path/to/file2
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</comment>
                            <comment id="114646" author="uselton" created="Thu, 7 May 2015 20:12:46 +0000"  >&lt;p&gt;I would make to modifications:&lt;/p&gt;

&lt;p&gt;client1:&lt;br/&gt;
dd if=/dev/zero of=/lustre/path/to/touchTest bs=1024 count=1024&lt;/p&gt;

&lt;p&gt;That way there is definitely stuff out on the OSTs and you will need to get the layout on client2.&lt;/p&gt;

&lt;p&gt;cleint2:&lt;br/&gt;
touch -c /lustre/path/to/touchTest&lt;/p&gt;

&lt;p&gt;You want to go after that same file. The path lookup may have the MDS ask for locks back from client1.&lt;br/&gt;
Once that is done I see these RPCs:&lt;/p&gt;

&lt;p&gt;11:18:41.986718 MDS     &amp;lt;- Clien2 Lustre 650 MDS_REINT request &lt;span class=&quot;error&quot;&gt;&amp;#91;REINT_SETATTR&amp;#93;&lt;/span&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;MINMODE&amp;#93;&lt;/span&gt;&lt;br/&gt;
11:18:41.986882 MDS -&amp;gt;     Clien2 Lustre 586 MDS_REINT reply &lt;br/&gt;
11:18:41.987461 MDS     &amp;lt;- Clien2 LustreBUG 538 LDLM_ENQUEUE request &lt;span class=&quot;error&quot;&gt;&amp;#91;Concurrent Read&amp;#93;&lt;/span&gt;[ intent : ]&lt;br/&gt;
11:18:41.987597 MDS -&amp;gt;     Clien2 Lustre 530 LDLM_ENQUEUE reply &lt;span class=&quot;error&quot;&gt;&amp;#91;Concurrent Read&amp;#93;&lt;/span&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;Malformed Packet&amp;#93;&lt;/span&gt;&lt;br/&gt;
11:18:41.988215 MDS     &amp;lt;- Clien2 Lustre 626 MDS_GETXATTR request  filename : trusted.lov&lt;br/&gt;
11:18:41.988315 MDS -&amp;gt;     Clien2 Lustre 634 MDS_GETXATTR reply &lt;br/&gt;
11:18:41.989389 OSS     &amp;lt;- Clien2 Lustre 602 OST_SETATTR request &lt;br/&gt;
11:18:41.989698 OSS -&amp;gt;     Clien2 Lustre 562 OST_SETATTR reply &lt;/p&gt;

&lt;p&gt;It is the LDLM_ENQUE that has the problem. The request has LustreBUG and the reply has &lt;span class=&quot;error&quot;&gt;&amp;#91;Malformed Packet&amp;#93;&lt;/span&gt;. The detailed breakouts of those two messages would help me with my protocol doc.&lt;br/&gt;
-A&lt;/p&gt;</comment>
                            <comment id="114733" author="gerrit" created="Fri, 8 May 2015 15:45:58 +0000"  >&lt;p&gt;Nathaniel Clark (nathaniel.l.clark@intel.com) uploaded a new patch: &lt;a href=&quot;http://review.whamcloud.com/14732&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/14732&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-6582&quot; title=&quot;Wireshark fails to parse LDLM_ENQUEUE RPC - likely for layout lock&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-6582&quot;&gt;&lt;del&gt;LU-6582&lt;/del&gt;&lt;/a&gt; wireshark: Add new LDLM intent bits&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: 1e492ba077a2e8d6ead417928562737488cd9f4e&lt;/p&gt;</comment>
                            <comment id="198028" author="gerrit" created="Sat, 3 Jun 2017 04:00:19 +0000"  >&lt;p&gt;Oleg Drokin (oleg.drokin@intel.com) merged in patch &lt;a href=&quot;https://review.whamcloud.com/14732/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/14732/&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-6582&quot; title=&quot;Wireshark fails to parse LDLM_ENQUEUE RPC - likely for layout lock&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-6582&quot;&gt;&lt;del&gt;LU-6582&lt;/del&gt;&lt;/a&gt; wireshark: Add new LDLM intent bits&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: &lt;br/&gt;
Commit: 05e3d5243425c02796d83dfd8d1487e73e2c1f1f&lt;/p&gt;</comment>
                            <comment id="198057" author="pjones" created="Sat, 3 Jun 2017 04:45:05 +0000"  >&lt;p&gt;Landed for 2.10&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="30456">LU-6671</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="29041">LU-6353</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|hzxcrz:</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>