Resilvering
conceptResilvering is what happens after you swap in a replacement disk: ZFS refills it from the surviving team members. Older storage systems rebuild a replacement by blindly copying the entire disk, end to end, because they have no idea which parts hold anything. ZFS knows exactly what's real data, so a resilver copies the data—not the disk—and fingerprint-checks every piece as it goes ("resilvering only examines data that ZFS knows to be out of date"—zpool-scrub(8)). A half-full pool recovers in roughly half the time. And the time genuinely matters: until the resilver finishes, you're running with less protection than you paid for.
Living through one: the pool stays up and serving—a resilver is a
background process, visible in zpool status with progress and an
estimate (early estimates lie; trust them only after they settle). The
system deliberately throttles resilver I/O behind live traffic, so a busy
pool resilvers slower. Don't reboot casually mid-resilver—it resumes, but
the window extends.
Vdev geometry sets the character of the event: a mirror resilver is a straight copy from the healthy twin—fast, gentle. A RAIDZ resilver reconstructs the missing disk from all survivors, hammering every one of them for hours or days at exactly the moment redundancy is reduced—correlated disks (same batch, same age) make that a real stress test. This asymmetry is a load-bearing input to the mirrors-vs-RAIDZ decision.