troubleshoot-zfs

Diagnose ZFS pool and performance incidents using Netdata-observed metrics via MCP queries.

1|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/netdata/skills --skill troubleshoot-zfs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: troubleshoot-zfs
Source: https://github.com/netdata/skills/tree/main/skills/troubleshoot-zfs
Command: npx skills add https://github.com/netdata/skills --skill troubleshoot-zfs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you quickly triage and remediate ZFS performance and health incidents by identifying the most likely failure archetype and verifying it with Netdata-observed signals.

Core Features & Use Cases

  • Structured ZFS triage for core failure archetypes: pool health degradation, capacity-fragmentation cliff, TXG sync hang, ARC memory starvation, silent data corruption, and ZIL/SLOG bottlenecks.
  • Netdata + MCP query-driven diagnostics: pulls the relevant MCP signals for pool health, per-vdev state and errors, I/O operations/latency/queue depth, and internal-state signals, then routes you through the operator playbook-style decision tree.
  • Signal verification before and after remediation: re-runs the same MCP queries to confirm the system returns to expected ranges rather than stopping at the first anomaly.

Quick Start

Use this skill when you see a ZFS pool or service behaving abnormally, and ask an AI coding agent to troubleshoot by querying Netdata via MCP and following the remediation path for the matching failure archetype.

Frequently Asked Questions about troubleshoot-zfs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot ZFS pool degradation and performance incidents using observability metrics?

Troubleshoot ZFS pool degradation by querying Netdata metrics via MCP to identify failure archetypes like fragmentation collapse, TXG sync hangs, or ARC memory starvation. It follows an operator playbook decision tree to route diagnostics and verify remediation.

Why does ZFS experience write freezes and high fsync latency during heavy workloads?

ZFS write freezes and fsync latency spikes are often caused by TXG sync hangs or ZIL/SLOG bottlenecks. This skill diagnoses these incidents by analyzing Netdata-observed I/O latency, queue depth, and internal ZFS state metrics to verify the root cause.

How can I detect silent data corruption and ARC memory starvation in ZFS?

Detect silent ZFS data corruption and ARC memory starvation by analyzing checksum errors and system memory pressure signals. This skill queries Netdata MCP for ZFS availability, errors, and resource utilization to confirm if ARC size is causing OOM events.

Can I verify ZFS pool health and confirm remediation success using Netdata?

You can verify ZFS pool health and remediation success using Netdata by re-running the same MCP queries. This confirms per-vdev state, errors, and throughput return to expected ranges rather than stopping at the first detected anomaly.

What is the best way to diagnose ZFS fragmentation-driven write amplification collapse?

Diagnose ZFS fragmentation-driven write amplification collapse by evaluating capacity limits and throughput metrics. This skill uses Netdata signals to verify if fragmentation has pushed the pool over a performance cliff and routes you through the remediation path.