The reply message conveys 'statfs' data when it succeeds, and an error
code if it doesn't.
-.OST_STATFS Generic Packet Structure
-image::ost-statfs-generic.png["OST_STATFS Generic Packet Structure",height=100]
+.OST_STATFS Request Packet Structure
+image::ost-statfs-request.png["OST_STATFS Request Packet Structure",height=50]
//////////////////////////////////////////////////////////////////////
-The ost-statfs-generic.png diagram resembles this text art:
+The ost-statfs-request.png diagram resembles this text art:
OST_STATFS:
--request------
| ptlrpc_body |
---------------
+//////////////////////////////////////////////////////////////////////
+
+'ptlrpc_body'::
+RPC descriptor. See <<struct-ptlrpc-body>>.
+
+.OST_STATFS Reply Packet Structure
+image::ost-statfs-reply.png["OST_STATFS Reply Packet Structure",height=50]
+
+//////////////////////////////////////////////////////////////////////
+The ost-statfs-reply.png diagram resembles this text art:
+
+ OST_STATFS:
--reply---------------------
| ptlrpc_body | obd_statfs |
----------------------------
//////////////////////////////////////////////////////////////////////
-'ptlrpc_body':: RPC descriptor. Only the 'pb_opc' value (OST_STATFS =
-41) is directly relevant to the OST_STATFS request message. The rest
-of the 'ptlrpc_body' fields handle generic information about the
-RPC, as discussed in <<struct-ptlrpc-body>>, including generic error
-conditions. In a normal reply ('pb_type' = PTL_RPC_MSG_REPLY) the
-'pb_status' field is 0. The one error that can be returned in
-'pb_status' that is speficially from OST_STATFS' handling is -ENOMEM,
-which occurs if there is not enough memory to allocate a temporary
-buffer for the 'statfs' data.
+'ptlrpc_body'::
+RPC descriptor. See <<struct-ptlrpc-body>>.
include::struct_obd_statfs.txt[]