1pidpersec(8)                System Manager's Manual               pidpersec(8)
2
3
4

NAME

6       mdflush - Trace md flush events. Uses Linux eBPF/bcc.
7

SYNOPSIS

9       mdflush
10

DESCRIPTION

12       This  tool  traces flush events by md, the Linux multiple device driver
13       (software RAID). The timestamp and md device for the flush are printed.
14       Knowing  when  these  flushes happen can be useful for correlation with
15       unexplained spikes in disk latency.
16
17       This works by tracing  the  kernel  md_flush_request()  function  using
18       dynamic  tracing,  and  will need updating to match any changes to this
19       function.
20
21       Note that the flushes themselves are likely to originate from higher in
22       the I/O stack, such as from the file systems.
23
24       Since this uses BPF, only the root user can use this tool.
25

REQUIREMENTS

27       CONFIG_BPF and bcc.
28

EXAMPLES

30       Trace md flush events:
31              # mdflush
32

FIELDS

34       TIME   Time of the flush event (HH:MM:SS).
35
36       PID    The  process  ID that was on-CPU when the event was issued. This
37              may identify the cause of the flush (eg,  the  "sync"  command),
38              but will often identify a kernel worker thread that was managing
39              I/O.
40
41       COMM   The command name for the PID.
42
43       DEVICE The md device name.
44

OVERHEAD

46       Expected to be negligible.
47

SOURCE

49       This is from bcc.
50
51              https://github.com/iovisor/bcc
52
53       Also look in the bcc distribution for a  companion  _examples.txt  file
54       containing example usage, output, and commentary for this tool.
55

OS

57       Linux
58

STABILITY

60       Unstable - in development.
61

AUTHOR

63       Brendan Gregg
64

SEE ALSO

66       biosnoop(8)
67
68
69
70USER COMMANDS                     2016-02-13                      pidpersec(8)
Impressum