include::struct_lu_fid.txt[]
-The 'mbo_handle' field indicates the identity of an open file related
-to the operation, if any. If there is no lock then it is just 0.
+*Returning to the 'mdt_body' structure the remaining fields are as
+follows.*
+
+The 'mbo_handle' field indicates the identity of the previously
+acquired lock for an open file, if any, that is the subject of the
+operation. If there is no lock then it is just 0.
The 'mbo_valid' field identifies which of the remaining fields are
actually in force. The flags in 'mbo_valid' are:
Which flag is associated with which field is indicated in the comments
beside the fields in the struct definition above. The fields without
-corresponding flags in the 'mbo_valid' field should be considered
-valid, though I'm not sure how much they actually get used.
+corresponding flags in the 'mbo_valid' field are also 'valid'.
Many of the fields have names and meanings that correspond directly to
those in 'struct mdt_rec_setattr' (ex. 'atime', 'size', 'mode',
The 'mbo_aclsize' field indicates the size of the POSIX access control
lists (ACLs) in bytes.
-The 'mbo_max_mdsize' field indicates the maximu size of the file layout,
+The 'mbo_max_mdsize' field indicates the maximum size of the file layout,
as described in <<struct-lov-mds-md>>
-The 'mbo_max_cookiesize' field is unused since Lustre 2.4. It formerly
-held the maximum permissible size of llog cookies for destroyed OST objectb
-
+The 'mbo_max_cookiesize' field is unused since Lustre 2.4. It
+formerly held the maximum permissible size of llog cookies for
+destroyed OST objects.