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

# [NAME](#NAME)

syncsnoop - Trace sync() syscall. Uses Linux eBPF/bcc.

# [SYNOPSIS](#SYNOPSIS)

**syncsnoop**

# [DESCRIPTION](#DESCRIPTION)

syncsnoop traces calls to sync(), which flushes file system buffers to storage devices. These calls can cause performance perturbations, and it can be useful to know if they are happening and how frequently.

This works by tracing the kernel sys\_sync() function using dynamic tracing, and will need updating to match any changes to this function.

This makes use of a Linux 4.4 feature (bpf\_perf\_event\_output()); for kernels older than 4.4, see the version under tools/old, which uses an older mechanism.

This program is also a basic example of eBPF/bcc.

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

# [REQUIREMENTS](#REQUIREMENTS)

CONFIG\_BPF and bcc.

# [EXAMPLES](#EXAMPLES)

[Trace calls to sync():](#Trace)

\# **syncsnoop**

# [FIELDS](#FIELDS)

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

Time of the call, in seconds.

[CALL](#CALL)

Call traced.

# [OVERHEAD](#OVERHEAD)

This traces the kernel sync function and prints output for each event. As the rate of this is generally expected to be low (&lt;&lt; 100/s), the overhead is also expected to be negligible.

# [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)

Brendan Gregg, original BCC Python version Tiago Ilieve, CO-RE version

# [SEE ALSO](#SEE_ALSO)

[iostat(1)](/man/enterprise-packages/bcc/iostat.1)

2015-08-18 USER COMMANDS

---

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