Skip to content

ZFS Pools

gitsync edited this page Jul 14, 2026 · 1 revision

The ZFS Pools page manages every pool on the system — creation, expansion, caching, scrubs, and guided recovery.

ZFS Pools page

Pool types

VDEV type Disks required Fault tolerance
Stripe 1+ None — any single disk loss destroys the pool
Mirror 2+ Up to N-1 disks per mirror group
RAIDZ1 3+ 1 disk per RAIDZ group
RAIDZ2 4+ 2 disks per RAIDZ group
RAIDZ3 5+ 3 disks per RAIDZ group — maximum protection, 9+ disks recommended

Creating a pool

  1. Click + Pool
  2. Select a VDEV type
  3. Pick the member disks (only disks not already in a pool are listed)
  4. Optionally configure ashift (12 = 4K sectors), compression (lz4 recommended), dedup (high RAM cost), and encryption
  5. Click Create — pool creation runs in the background with live progress

Pool operations

Operation Where Notes
Import existing pool ⋮ menu → Import ZFS Pool Scans for importable pools
Expand pool Add Device Adds disks / VDEVs to an existing pool
Upgrade feature flags Upgrade (shown when available) One-way; enables new ZFS features
Disconnect (export) pool ⋮ menu → Disconnect ZFS Pool Safe for moving to another host
Destroy pool ⋮ menu → Destroy Pool Requires typing the pool name; irreversible

The portal fully supports multiple pools — the top-bar pool selector and per-pool dashboard tabs follow your selection.

Cache devices, SLOG, and hot spares

Cache Config

Open Cache Config → Disk Cache:

  • L2ARC — level-2 read cache on a fast SSD; helps read-heavy datasets that don't fit in RAM
  • ZIL (SLOG) — separate write intent log; reduces latency for synchronous writes (databases, VMs, NFS sync)
  • Hot spares — idle disks that ZFS automatically resilvers onto when a member disk fails

Add or remove cache/log/spare devices without taking the pool offline.

ARC Level 1 (memory cache)

Cache Config → ARC Level 1 (Memory) shows current ARC size, hit rate, and miss rate, and lets you set minimum/maximum ARC size limits. Changes apply immediately and persist across reboots. This is an advanced tuning knob — incorrect values can hurt performance.

Scrub management

ZFS scrub reads every block in the pool and verifies checksums, catching silent data corruption.

  • Start / Stop a scrub from the Scrub control on the pool page (progress is shown live)
  • Schedule recurring scrubs: weekly, bi-weekly, monthly, every 2 months, or every 4 months

A monthly scrub is a good default for most home/office deployments.

Pool Fixer Wizard

When a pool needs attention, the Pool Fixer Wizard button appears automatically in the pool page header. It diagnoses the situation and proposes a one-click, guided fix — you always see exactly what will be run and why before confirming.

Pool Fixer Wizard — checksum errors

Situation What the wizard proposes
ONLINE, device errors logged (e.g. checksum errors a scrub repaired) Shows a per-device Read/Write/Cksum error table, explains whether your data is intact, and offers zpool clear — with the advice to replace the disk if the same one keeps accumulating errors
SUSPENDED, disks visible again Clears the error state (and brings disks back online) after a cable/power/HBA incident
DEGRADED — disk offline but present Brings the disk back online; ZFS resilvers automatically
DEGRADED — disk missing/dead Guides you through replacing the failed disk with a new one (zpool replace)
Anything else Shows the raw zpool status output and links the relevant OpenZFS recovery documentation

If the pool reports permanent data errors, the wizard tells you up front and points you to zpool status -v to identify affected files for restore from backup.

Related pages

Clone this wiki locally