1 RPC 40: MDS GETSTATUS - get the status from a target
2 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
5 Get the attributes of the mountpoint of the file system.
7 .MDS_GETSTATUS Request Packet Structure
8 image::mds-getstatus-request.png["MDS_GETSTATUS Request Packet Structure",height=50]
10 //////////////////////////////////////////////////////////////////////
11 The mds-getstatus-request.png diagram resembles this text art:
14 --request-----------------
15 | ptlrpc_body | mdt_body |
16 --------------------------
17 //////////////////////////////////////////////////////////////////////
20 RPC descriptor. See <<struct-ptlrpc-body>>.
23 See <<struct-mdt-body>>.
25 In the request message, the 'mdt_body' is normally empty.
27 .MDS_GETSTATUS Reply Packet Structure
28 image::mds-getstatus-reply.png["MDS_GETSTATUS Reply Packet Structure",height=50]
30 //////////////////////////////////////////////////////////////////////
31 The mds-getstatus-reply.png diagram resembles this text art:
34 --reply-------------------
35 | ptlrpc_body | mdt_body |
36 --------------------------
37 //////////////////////////////////////////////////////////////////////
40 RPC descriptor. See <<struct-ptlrpc-body>>.
43 See <<struct-mdt-body>>.
45 In the reply message, the 'mdt_body' contains only the FID of the
46 filesystem ROOT in 'mbo_fid1'. The client can then use the returned
47 FID to fetch inode attributes for the root inode of the local