2 <-------MDS_REINT
//////////////////////////////////////////////////////////////////////
-1 - The client issues an MDS_REINT with the REINT_SETXATTR
-sub-operation.
+*1 - The client issues an MDS_REINT with the REINT_SETXATTR
+sub-operation.*
In addition to the 'ptlrpc_body' (RPC message header), the MDS_REINT
request RPC from the client has the REINT structure
'mdt_rec_setxattr', the name of the extended attribute in question,
the extended attribute data to put in place, and a lock request
'ldlm_request'. For a detailed discussion of all the fields in the
-'mdt_rec_setxattr' and 'ldlm_request' refer to <<mdt-rec-setxattr>>
-and <<struct-ldlm-request>>.
+'mdt_rec_setxattr' and 'ldlm_request' refer to
+<<struct-mdt-rec-setxattr>> and <<struct-ldlm-request>>.
.MDS_REINT:REINT_SETXATTR Request Packet Structure
image::mds-reint-setxattr-request.png["MDS_REINT:REINT_SETXATTR Request Packet Structure",height=50]
-------------------------------------------------
//////////////////////////////////////////////////////////////////////
+See <<mds-reint-rpc>>.
+
The 'setxattr' wants to set the 'ctime' associated with the EA update
as well, so the one 'sx_valid' flag it uses is OBD_MD_FLCTIME
(0x00008). The 'sx_valid' field also has the OBD_MD_FLXATTR
indicating early lock cancellation is not being used. This may be a
bug in the code for that instance.
-2 - The MDS_REINT reply acknowledges the updated attributes.
+*2 - The MDS_REINT reply acknowledges the updated attributes.*
In addition to the 'ptlrpc_body' (RPC message header), the MDS_REINT
reply RPC to the client has the 'mdt_body' structure. For a detailed