Lines Matching +full:system +full:- +full:trace

1 .TH zfsslower 8  "2016-02-11" "USER COMMANDS"
3 zfsslower \- Trace slow zfs file operations, with per-event details.
5 .B zfsslower [\-h] [\-j] [\-p PID] [min_ms]
26 \-p PID
27 Trace this PID only.
30 Minimum I/O latency (duration) to trace, in milliseconds. Default is 10 ms.
33 Trace synchronous file reads and writes slower than 10 ms:
37 Trace slower than 1 ms:
41 Trace slower than 1 ms, and output just the fields in parsable format (csv):
43 .B zfsslower \-j 1
45 Trace all file reads and writes (warning: the output will be verbose):
49 Trace slower than 1 ms, for PID 181 only:
51 .B zfsslower \-p 181 1
75 file system CPU cycles, file system locks, run queue latency, etc. It's a more
77 system I/O, than to measure this down at the block device interface.
80 A cached kernel file name (comes from dentry->d_iname).
83 Completion timestamp, microseconds (\-j only).
86 File offset, bytes (\-j only).
89 Latency (duration) of the I/O, in microseconds (\-j only).
91 This adds low-overhead instrumentation to these ZFS operations,
92 including reads and writes from the file system cache. Such reads and writes
96 continues to be a problem, consider switching to a tool that prints in-kernel
112 Unstable - in development.