zed

Start zed in foreground mode

$ sudo zed -F

$ sudo zed -v

$ sudo zed -M

$ sudo zed -d [/etc/zfs/zed.d]

zed [-FhMvV] [-c conffile] [-d confdir] [-I idle] [-p pidfile] [-P path] [-s statefile]

zed (ZFS Event Daemon) monitors ZFS kernel events and executes scripts in response. It listens for events like scrub completion, device failures, pool imports, and data errors, then runs corresponding handler scripts.
Scripts are stored in /etc/zfs/zed.d/ with naming convention event-name.sh. Enabled scripts are symlinked to be active. Common events include:
- resilver.finish - Resilver completed
- scrub.finish - Scrub completed
- statechange - Pool state changed
- data - Data errors detected
zed enables automated responses to ZFS events like sending email notifications on errors or running custom maintenance scripts.

-c conffile

Read configuration from specified file

Read enabled scripts from directory (default: /etc/zfs/zed.d)

Run in foreground, don't daemonize

Display help message

Idle timeout in seconds for script execution

Ignore missing state file

Write process ID to file

Set PATH for script execution

Write state to file

Verbose mode, log events to stderr

Display version

zed must run as root to receive kernel events and access pool information.
Script execution is serialized by default. Long-running scripts can delay processing of subsequent events.
Poorly written event scripts can cause system issues. Test scripts thoroughly before enabling.
On systemd systems, zed typically runs as a systemd service (zfs-zed.service).

zfs(8), zpool(8), zpool-events(8)