https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-6671 Lustre <p>The attached file is the tcpdump on a client where I ran a "truncate" test ('multiop &lt;file&gt; OTc 1024'). After the MDS_REINT request and reply there is an LDLM_ENQUEUE request and reply for an extent lock. The "verbose" tshark output shows in the header that there are three buffers:</p> <p> Lm Buflens: 152<br/> Lm Buflens: 112<br/> Lm Buflens: 56</p> <p>But only the first two 'ptlrpc_body' and 'ldlm_reply' get decoded or even mentioned. I am guessing the thrid buffer is an ost_lvb, but I could well be wrong.<br/> -Andrew</p> LU-6671

Wireshark: LDLM_ENQUEUE reply with undecoded buffer

Bug Minor Resolved Fixed Nathaniel Clark Andrew Uselton wireshark Mon, 1 Jun 2015 22:55:09 +0000 Wed, 19 Jul 2017 15:48:50 +0000 Wed, 19 Jul 2017 15:48:50 +0000 Lustre 2.11.0 0 7 <p>Nathaniel Clark (nathaniel.l.clark@intel.com) uploaded a new patch: <a href="http://review.whamcloud.com/18061" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/18061</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-6671" title="Wireshark: LDLM_ENQUEUE reply with undecoded buffer" class="issue-link" data-issue-key="LU-6671"><del>LU-6671</del></a> wireshark: Process mds_md entries<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 9955da227dd414f1441cf659861a70a4f5c4de77</p> <p>Amir Shehata (amir.shehata@intel.com) uploaded a new patch: <a href="http://review.whamcloud.com/22422" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/22422</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-6671" title="Wireshark: LDLM_ENQUEUE reply with undecoded buffer" class="issue-link" data-issue-key="LU-6671"><del>LU-6671</del></a> wireshark: Fix compile issues<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 687590ae46077888a0bcaf0cdbdf8670214c06e8</p> <p>Nathan Lavender,<br/> there are a number of patches that add wireshark decoding functionality under this ticket in Gerrit:<br/> <a href="http://review.whamcloud.com/14552" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/14552</a> "<a href="https://jira.whamcloud.com/browse/LU-4378" title="Add HSM message parsing to wireshark plugins" class="issue-link" data-issue-key="LU-4378"><del>LU-4378</del></a> wireshark: Add parsing for HSM commands"<br/> <a href="http://review.whamcloud.com/14732" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/14732</a> "<a href="https://jira.whamcloud.com/browse/LU-6582" title="Wireshark fails to parse LDLM_ENQUEUE RPC - likely for layout lock" class="issue-link" data-issue-key="LU-6582"><del>LU-6582</del></a> wireshark: Add new LDLM intent bits"<br/> <a href="http://review.whamcloud.com/14961" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/14961</a> "<a href="https://jira.whamcloud.com/browse/LU-6648" title="Wireshark 1.8.10 does not correctly parse LDLM_ENQUEUE intent : getxattr " class="issue-link" data-issue-key="LU-6648"><del>LU-6648</del></a> wireshark: Process ldlm intent getxattr"<br/> <a href="http://review.whamcloud.com/18061" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/18061</a> "<a href="https://jira.whamcloud.com/browse/LU-6671" title="Wireshark: LDLM_ENQUEUE reply with undecoded buffer" class="issue-link" data-issue-key="LU-6671"><del>LU-6671</del></a> wireshark: Process mds_md entries"</p> <p>and separately two patches that add the ladvise functionality (the second one fixes breakage from the first):</p> <p><a href="http://review.whamcloud.com/10029" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/10029</a> "<a href="https://jira.whamcloud.com/browse/LU-4931" title="New feature of giving server/storage side advice of accessing file" class="issue-link" data-issue-key="LU-4931"><del>LU-4931</del></a> ladvise: Add feature of giving file access advices" (packet-lustre.c part only)<br/> <a href="http://review.whamcloud.com/22074" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/22074</a> "<a href="https://jira.whamcloud.com/browse/LU-8499" title="wireshark plugins don&#39;t build any more" class="issue-link" data-issue-key="LU-8499"><del>LU-8499</del></a> wireshark: fix packet-lustre so it compiles"</p> <p>It would be great to include these into the packet-lustre.c update that you are working on to push upstream along with the sptlrpc decoders. Is that an ongoing process, or is it currently on hold?</p> <p>Andreas, recent progress has been slow since the focus has been on the Shared Secret Key functionality itself, but yes this is an ongoing process. From an initial review of the the patches, I don't see any issues with including them in the packet-lustre.c update we're working on and pushing them upstream along with it sounds great. We'll plan on doing that and will report back if we encounter difficulties.</p> <p>Oleg Drokin (oleg.drokin@intel.com) merged in patch <a href="https://review.whamcloud.com/18061/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/18061/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-6671" title="Wireshark: LDLM_ENQUEUE reply with undecoded buffer" class="issue-link" data-issue-key="LU-6671"><del>LU-6671</del></a> wireshark: Process mds_md entries<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: 57661182dbcdc2ec92dfafdeded078ab8ef8b7c6</p> <p>Can this ticket be marked as resolved with the most recent landing?</p> <p>Sure, I've got no outstanding wireshark patches.</p> Related LU-6582 LU-6648 LU-4931 LU-4378 LU-8499 LU-6353 Development Rank 1|hzxenr: Rank (Obsolete) 9223372036854775807 Severity