From 6c17de9edd8adeb0c0d1142ce5d576af50504087 Mon Sep 17 00:00:00 2001 From: Richard Henwood Date: Mon, 28 Nov 2011 14:57:04 -0600 Subject: [PATCH] LUDOC-4 client stats file values description. Description of the values returned by the command: lctl get_param llite.*.stats. Updated to include 2.2 stats from LU-334. Signed-off-by: Richard Henwood Change-Id: I85f758dfcc0a4f76a280b96d50acf1bd0363562a --- LustreProc.xml | 205 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 204 insertions(+), 1 deletion(-) diff --git a/LustreProc.xml b/LustreProc.xml index da1ff90..0e0cbe5 100644 --- a/LustreProc.xml +++ b/LustreProc.xml @@ -469,7 +469,7 @@ blocksizefilesfree max_dirty_mb ost_server_uuid stats ... and so on. RPC stream tunables are described below. /proc/fs/lustre/osc/<object name>/max_dirty_mb - This tunable controls how many MBs of dirty data can be written and queued up in the OSC. POSIX file writes that are cached contribute to this count. When the limit is reached, additional writes stall until previously-cached writes are written to the server. This may be changed by writing a single ASCII integer to the file. Only values between 0 and 512 are allowable. If 0 is given, no writes are cached. Performance suffers noticeably unless you use large writes (1 MB or more). + This tunable controls how many MBs of dirty data can be written and queued up in the OSC. POSIX file writes that are cached contribute to this count. When the limit is reached, additional writes stall until previously-cached writes are written to the server. This may be changed by writing a single ASCII integer to the file. Only values between 0 and 512 are allowable. If 0 is given, no writes are cached. Performance suffers noticeably unless you use large writes (1 MB or more). /proc/fs/lustre/osc/<object name>/cur_dirty_bytes This tunable is a read-only value that returns the current amount of bytes written and cached on this OSC. /proc/fs/lustre/osc/<object name>/max_pages_per_rpc @@ -652,6 +652,209 @@ R 8385 500 600 100 +
+ <indexterm><primary>proc</primary><secondary>client stats</secondary></indexterm>Client stats + The stats parameter maintains statistics of activity across the VFS interface of the Lustre file system. Only non-zero parameters are displayed in the file. This section of the manual covers the statistics that will accumulate during typical operation of a client. + Client statistics are enabled by default. The statistics can be cleared by echoing an empty string into the stats file or with the command: lctl set_param llite.*.stats=0. Statistics for an individual file system can be displayed, for example: + # cat /proc/fs/lustre/llite/lustre-ffff88000449a800/stats +snapshot_time 1308343279.169704 secs.usecs +dirty_pages_hits 14819716 samples [regs] +dirty_pages_misses 81473472 samples [regs] +read_bytes 36502963 samples [bytes] 1 26843582 55488794 +write_bytes 22985001 samples [bytes] 0 125912 3379002 +brw_read 2279 samples [pages] 1 1 2270 +ioctl 186749 samples [regs] +open 3304805 samples [regs] +close 3331323 samples [regs] +seek 48222475 samples [regs] +fsync 963 samples [regs] +truncate 9073 samples [regs] +setxattr 19059 samples [regs] +getxattr 61169 samples [regs] + +Statistics for all mounted file systems can be discovered by issuing the lctl command: lctl get_param llite.*.stats + + + + + + + + Field + + + Description + + + + + + + snapshot_time + + + Unix epoch instant the stats file was read. + + + + + dirty_page_hits + + + A count of the number of write operations that have been satisfied by the dirty page cache. See for dirty cache behavior in Lustre. + + + + + dirty_page_misses + + + A count of the number of write operations that were not satisfied by the dirty page cache. + + + + + read_bytes + + + A count of the number of read operations that have occurred (samples). Three additional parameters are given: + + + min + The minimum number of bytes read in a single request since the counter was reset. + + + + max + The maximum number of bytes read in a single request since the counter was reset. + + + + sum + The accumulated sum of bytes of all read requests since the counter was reset. + + + + + + + + write_bytes + + + A count of the number of write operations that have occurred (samples). Three additional parameters are given: + + + min + The minimum number of bytes written in a single request since the counter was reset. + + + + max + The maximum number of bytes written in a single request since the counter was reset. + + + + sum + The accumulated sum of bytes of all write requests since the counter was reset. + + + + + + + + brw_read + + + A count of the number of pages that have been read. brw_ stats are only tallied when the lloop device driver is present. lloop device is not currently supported.Three additional parameters are given: + + + min + The minimum number of bytes read in a single brw read requests since the counter was reset. + + + + max + The maximum number of bytes read in a single brw read requests since the counter was reset. + + + + sum + The accumulated sum of bytes of all brw read requests since the counter was reset. + + + + + + + + ioctl + + + A count of the number of the combined file and directory ioctl operations. + + + + + open + + + A count of the number of open operations that have succeeded. + + + + + close + + + A count of the number of close operations that have succeeded. + + + + + seek + + + A count of the number of times seek has been called. + + + + + fsync + + + A count of the number of times fsync has been called. + + + + + truncate + + + A count of the total number of calls to both locked and lockless truncate. + + + + + setxattr + + + A count of the number of times ll_setxattr has been called. + + + + + getxattr + + + A count of the number of times ll_getxattr has been called. + + + + + +
<indexterm><primary>proc</primary><secondary>read/write survey</secondary></indexterm>Client Read-Write Extents Survey Client-Based I/O Extent Size Survey -- 1.8.3.1