Lustre 1.6 Operations Manual

pid inode goal result foundgrps cr \ merge tailbroken
2838 32801 4/12288/1 5/925/1 31 2 1 \ 0 0
2838 32802 4/12288/1 5/926/1 31 2 1 \ 1 2
2838 32803 4/12288/1 5/927/1 31 2 1 \ 0 0
2838 32804 4/12288/1 5/928/1 31 2 1 \ 1 32
2838 32805 4/12288/1 5/929/1 31 2 1 \ 0 0
2838 32806 4/12288/1 5/930/1 31 2 1 \ 1 2
2838 32807 4/12288/1 5/931/1 31 2 1 \ 0 0
2838 24579 3/12288/1 3/12289/1 11 1 1 \ 0 0
The parameters are described below:
Parameter
pid
inode
goal
result
found
grps
cr
queue
merge
tail
broken
Description
Process that made the allocation.
inode number allocated blocks
Initial request that came to mballoc (group/block-in-group/number-of-blocks)
What mballoc actually found for this request.
Number of free chunks mballoc found and measured before the final decision.
Number of groups mballoc scanned to satisfy the request.
Stage at which mballoc found the result:
0 - best in terms of resource allocation. The request was 1MB or larger and was
satisfied directly via the kernel buddy allocator.
1 - regular stage (good at resource consumption)
2 - fs is quite fragmented (not that bad at resource consumption)
3 - fs is very fragmented (worst at resource consumption)
Total bytes in active/queued sends.
Whether the request hit the goal. This is good as extents code can now merge
new blocks to existing extent, eliminating the need for extents tree growth.
Number of blocks left free after the allocation breaks large free chunks.
How large the broken chunk was.
Most customers are probably interested in found/cr. If cr is 0 1 and found is less
than 100, then mballoc is doing quite well.
Also, number-of-blocks-in-request (third number in the goal triple) can tell the
number of blocks requested by the obdfilter. If the obdfilter is doing a lot of small
requests (just few blocks), then either the client is processing input/output to a lot of
small files, or something may be wrong with the client (because it is better if client
sends large input/output requests). This can be investigated with the OSC
rpc_stats or OST brw_stats mentioned above.
Chapter 20 LustreProc 20-21