f2fsslower(8) System Manager's Manual f2fsslower(8)

# [NAME](#NAME)

f2fsslower - Trace slow f2fs file operations, with per-event details.

# [SYNOPSIS](#SYNOPSIS)

**f2fsslower \[-h] \[-s] \[-p PID] \[min\_ms]**

# [DESCRIPTION](#DESCRIPTION)

This tool traces common f2fs file operations: reads, writes, opens, and syncs. It measures the time spent in these operations, and prints details for each that exceeded a threshold.

WARNING: See the OVERHEAD section.

By default, a minimum millisecond threshold of 10 is used. If a threshold of 0 is used, all events are printed (warning: verbose).

Since this works by tracing the f2fs\_file\_operations interface functions, it will need updating to match any changes to these functions.

Since this uses BPF, only the root user can use this tool.

# [REQUIREMENTS](#REQUIREMENTS)

CONFIG\_BPF and bcc.

# [OPTIONS](#OPTIONS)

-p PID Trace this PID only.

[min\_ms](#min_ms)

Minimum I/O latency (duration) to trace, in milliseconds. Default is 10 ms.

# [EXAMPLES](#EXAMPLES)

[Trace synchronous file reads and writes slower than 10 ms:](#Trace)

\# **f2fsslower**

[Trace slower than 1 ms:](#Trace~2)

\# **f2fsslower 1**

[Trace slower than 1 ms, and output just the fields in parsable format (csv):](#Trace~3)

\# **f2fsslower -s 1**

[Trace all file reads and writes (warning: the output will be verbose):](#Trace~4)

\# **f2fsslower 0**

[Trace slower than 1 ms, for PID 181 only:](#Trace~5)

\# **f2fsslower -p 181 1**

# [FIELDS](#FIELDS)

[TIME(s)](#TIME%28s%29)

Time of I/O completion since the first I/O seen, in seconds.

[COMM](#COMM)

Process name.

[PID](#PID)

Process ID.

[T](#T)

Type of operation. R == read, W == write, O == open, S == fsync.

[OFF\_KB](#OFF_KB)

File offset for the I/O, in Kbytes.

[BYTES](#BYTES)

Size of I/O, in bytes.

[LAT(ms)](#LAT%28ms%29)

Latency (duration) of I/O, measured from when it was issued by VFS to the filesystem, to when it completed. This time is inclusive of block device I/O, file system CPU cycles, file system locks, run queue latency, etc. It's a more accurate measure of the latency suffered by applications performing file system I/O, than to measure this down at the block device interface.

[FILENAME](#FILENAME)

A cached kernel file name (comes from dentry->d\_name.name).

[ENDTIME\_us](#ENDTIME_us)

Completion timestamp, microseconds (-s only).

[OFFSET\_b](#OFFSET_b)

File offset, bytes (-s only).

[LATENCY\_us](#LATENCY_us)

Latency (duration) of the I/O, in microseconds (-s only).

# [OVERHEAD](#OVERHEAD)

This adds low-overhead instrumentation to these f2fs operations, including reads and writes from the file system cache. Such reads and writes can be very frequent (depending on the workload; eg, 1M/sec), at which point the overhead of this tool (even if it prints no "slower" events) can begin to become significant. Measure and quantify before use. If this continues to be a problem, consider switching to a tool that prints in-kernel summaries only.

Note that the overhead of this tool should be less than [fileslower(8)](/man/enterprise-packages/bcc/fileslower.8), as this tool targets f2fs functions only, and not all file read/write paths (which can include socket I/O).

# [SOURCE](#SOURCE)

This is from bcc.

https://github.com/iovisor/bcc

Also look in the bcc distribution for a companion \_examples.txt file containing example usage, output, and commentary for this tool.

# [OS](#OS)

Linux

# [STABILITY](#STABILITY)

Unstable - in development.

# [AUTHOR](#AUTHOR)

Ting Zhang

# [SEE ALSO](#SEE_ALSO)

[biosnoop(8)](/man/enterprise-packages/bcc/biosnoop.8), [funccount(8)](/man/enterprise-packages/bcc/funccount.8), [fileslower(8)](/man/enterprise-packages/bcc/fileslower.8)

2022-08-15 USER COMMANDS

---

Document: f2fsslower(8) from bcc 0.37.0-r2 (Chainguard OS)
Source: https://github.com/iovisor/bcc