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-3597 Lustre <p>On v2_4_52_0-2-g809d46b, the last MDS opcode in lustre_idl.h is MDS_SWAP_LAYOUTS = 61 (added by 4af3ab19), while the last MDS opcode in packet-lustre.c is MDS_GET_INFO = 53. What is the mechanism for keeping these files in sync?</p> LU-3597

packet-lustre.c opcodes out of sync with lustre_idl.h

Bug Minor Resolved Fixed Nathaniel Clark John Hammond ptlrpc wireshark Tue, 16 Jul 2013 16:41:31 +0000 Wed, 16 Oct 2013 01:57:49 +0000 Wed, 16 Oct 2013 01:57:49 +0000 Lustre 2.5.0 Lustre 2.5.0 0 4 <p>The original thinking in the Wireshark support was we will want to push the Lustre support plugins upstream. As such we tried to make the contrib/wireshark directory self-contained and not dependent on any Lustre files. That makes keeping the opcodes in sync an manual process (as they will be when this is upstream).</p> <p>However, we are not sure when we will be working to push these upstream so creating a "temporary" dependancy on lustre_idl.h would probably be ok.</p> <p>It seems reasonable to have the wireshark plugin require lustre-devel (which is actually lustre-client) to build.</p> <p>Using lustre_idl.h may be more complicated due to <a href="https://jira.whamcloud.com/browse/LU-1606" title="lustre_idl.h does not compile in user-space" class="issue-link" data-issue-key="LU-1606"><del>LU-1606</del></a>.</p> <p>Here's just a basic update of MDS opcodes:<br/> <a href="http://review.whamcloud.com/7005" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/7005</a></p> <p>Patch landed to Master. If more work is needed in this ticket please let me know and I will reopen or create new ticket for follow on work.</p> Related LU-1606 Development Rank 1|hzvvif: Rank (Obsolete) 9121 Severity