[LU-6630] ldlm_intent_getattr_client RPC mbo_valid flags do not match those returned

Related — Tue, 13 Sep 2016 20:37:28 +0000

Attached is a Wireshark output of an interaction that shows LDLM_ENQUEUE request and reply with inconsistent mbo_valid flags. The attached output has the detailed field values of a sequence of RPCs that resulted (to and from a particular client) when an 'fstat' operation was carried out. This was from the command line:
multiop /lfs/andrew/testDir/fstatTest OSc
You will see path lookup RPCs first. Scroll down to the first mention of "intent : getattr". It will be the next LDLM_ENQUEUE RPC after the ones that do the open of "fstatTest". In the request RPC the mbo_valid field has '2768391860191', which is '0x28491036fdf'. This breaks out as the following 21 flags:

OBD_MD_FLID
OBD_MD_FLATIME
OBD_MD_FLMTIME
OBD_MD_FLCTIME
OBD_MD_FLSIZE
OBD_MD_FLBLKSZ
OBD_MD_FLMODE
OBD_MD_FLTYPE
OBD_MD_FLUID
OBD_MD_FLGID
OBD_MD_FLFLAGS
OBD_MD_FLNLINK
OBD_MD_FLGENER
OBD_MD_FLRDEV
OBD_MD_FLEASIZE
OBD_MD_FLGROUP
OBD_MD_FLDIREA
OBD_MD_FLMODEASIZE
OBD_MD_MEA
OBD_MD_FLACL
OBD_MD_FLMDSCAPA

The next RPC is the LDLM_ENQUEUE reply from the MDS to this request. In it the mbo_valid field is 551903440783 = 0x8080022f8f, which breaks out as these 13 flags:

OBD_MD_FLID
OBD_MD_FLATIME
OBD_MD_FLMTIME
OBD_MD_FLCTIME
OBD_MD_FLMODE
OBD_MD_FLTYPE
OBD_MD_FLUID
OBD_MD_FLGID
OBD_MD_FLFLAGS
OBD_MD_FLNLINK
OBD_MD_FLEASIZE
OBD_MD_FLMODEASIZE
OBD_MD_FLACL

A proper subset. Please explain the discrepancy. Andreas has suggested that the client request should list at_least all the field values that should be returned, but the MDT is not honoring that in its request. He speculated this may be a sign of dead code.

Whamcloud Community JIRA

[LU-6630] ldlm_intent_getattr_client RPC mbo_valid flags do not match those returned