LUDOC-296 protocol: remove internal details from descriptions

[doc/protocol.git] / mdt_body.txt

diff --git a/mdt_body.txt b/mdt_body.txt
index 1e31729..ecce92d 100644 (file)
--- a/mdt_body.txt
+++ b/mdt_body.txt
@@ -3,7 +3,7 @@ MDT Body
 [[struct-mdt-body]]
 
 An 'mdt_body' structure conveys information about the metadata for a
-resource.
+single resource, typically an MDT inode.
 
 ----
 struct mdt_body {
@@ -48,7 +48,7 @@ For an operation that involves two resources both the 'mbo_fid1' and
 'mbo_fid2' fields will be filled in. If the 'mdt_body' is part of an
 RPC affecting or involving only a single resource then 'mbo_fid1' will
 designate that resource and 'mbo_fid2' will be cleared (see
-<<file-id>>).
+<<struct-lu-fid>>).
 
 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.
@@ -100,9 +100,12 @@ The 'mbo_nlink' field gives the number of hard links to the resource.
 The 'mbo_eadatasize' field gives the size of the extended attributes,
 which hold such information as the resource's layout.
 
-The 'mbo_aclsize' field supports POSIX access control lists (ACLs).
+The 'mbo_aclsize' field indicates the size of the POSIX access control
+lists (ACLs) in bytes.
 
-The 'mbo_max_mdsize' field
+The 'mbo_max_mdsize' field indicates the maximu size of the file layout,
+as described in <<struct-lov-mds-md>>
 
-The 'mbo_max_cookiesize' field is unused.
+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