[LU-6686] tshark drops 'ost_lvb' from LDLM_ENQUEUE reply verbose output

• Status: Resolved
• Project: Lustre
• Type: Bug
• Priority: Minor
• Reporter: Andrew Uselton (Inactive)
• Assignee: WC Triage
• Resolution: Low Priority
• Severity: 3

Description

Attached is a tcpdump for an experiment running an 'fstat' ('multiop OSc') from the client. Look for the LDLM_ENQUEUE (intent : getattr) request and reply, then go on to the next LDLM_ENQUEUE request and reply. The latter is a request from the client to the OST for an extent lock. The reply is listed in the header as having three buffers:

Lm Bufflens: 152 - ptlrpc_body
Lm Bufflens: 112 - ldlm_reply
Lm Bufflens: 56 - ?what?

The third buffer is not included in the output at all. This is after an update with http://review.whamcloud.com/#/c/14961/ . Prior to that update the verbose output to tshark said "generic data". Now it doesn't even say that. I am pretty sure this is supposed to be a 'struct ost_lvb' (which is 56 bytes), but can't be absolutely sure.
-Andrew