RPC 40: MDS GETSTATUS - get the status from a target
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[[mds-getstatus-rpc]]

Get the attributes of the mount point of the file system.

.MDS_GETSTATUS Request Packet Structure
image::mds-getstatus-request.png["MDS_GETSTATUS Request Packet Structure",height=50]

//////////////////////////////////////////////////////////////////////
The mds-getstatus-request.png diagram resembles this text art:

       MDS_GETSTATUS:
      --request-----------------
      | ptlrpc_body | mdt_body |
      --------------------------
//////////////////////////////////////////////////////////////////////

'ptlrpc_body'::
RPC descriptor. See <<struct-ptlrpc-body>>.

'mdt_body'::
See <<struct-mdt-body>>.

In the request message, the 'mdt_body' is normally empty.

.MDS_GETSTATUS Reply Packet Structure
image::mds-getstatus-reply.png["MDS_GETSTATUS Reply Packet Structure",height=50]

//////////////////////////////////////////////////////////////////////
The mds-getstatus-reply.png diagram resembles this text art:

       MDS_GETSTATUS:
      --reply-------------------
      | ptlrpc_body | mdt_body |
      --------------------------
//////////////////////////////////////////////////////////////////////

'ptlrpc_body'::
RPC descriptor. See <<struct-ptlrpc-body>>.

'mdt_body'::
See <<struct-mdt-body>>.

In the reply message, the 'mdt_body' contains only the FID of the
file system ROOT in 'mbo_fid1'.  The client can then use the returned
FID to fetch inode attributes for the root inode of the local
mount point.