- bullseye 0.18.0+ds-2
- bullseye-backports 0.22.0+ds-2~bpo11+1
- testing 0.25.0+ds-2
- unstable 0.26.0+ds-1
- experimental 0.26.0+ds-2~experimental1
|pidpersec(8)||System Manager's Manual||pidpersec(8)|
mdflush - Trace md flush events. Uses Linux eBPF/bcc.
This tool traces flush events by md, the Linux multiple device driver (software RAID). The timestamp and md device for the flush are printed. Knowing when these flushes happen can be useful for correlation with unexplained spikes in disk latency.
This works by tracing the kernel md_flush_request() function using dynamic tracing, and will need updating to match any changes to this function.
Note that the flushes themselves are likely to originate from higher in the I/O stack, such as from the file systems.
Since this uses BPF, only the root user can use this tool.
CONFIG_BPF and bcc.
- Trace md flush events:
- # mdflush
- Time of the flush event (HH:MM:SS).
- The process ID that was on-CPU when the event was issued. This may identify the cause of the flush (eg, the "sync" command), but will often identify a kernel worker thread that was managing I/O.
- The command name for the PID.
- The md device name.
Expected to be negligible.
This is from bcc.
Also look in the bcc distribution for a companion _examples.txt file containing example usage, output, and commentary for this tool.
Unstable - in development.