ZFS, Actually Storage you can finally reason about.

The Vdev

concept
depth 2/4 − deeper + surface

From above, the pool looks like one undivided pot of storage. Underneath, ZFS never treats your disks as one big group. It binds them into small teams, and each team backs itself up. That team is a vdev ("virtual device"). A team might be two disks keeping identical copies (a mirror), a group of disks sharing recovery math so any one can die (RAIDZ), or— dangerously—one lone disk backing up nothing. A pool is built by joining teams together.

Here is the sentence this entire site most wants you to hold: spare copies exist only inside each team, never between teams—so losing any one whole team loses the whole pool. Not damaged. Gone. The pool spread everyone's data across all its teams, so a dead team is a bite out of everything.

This is why the classic homelab move—"the pool's getting full, I'll just add this spare disk"—is a trap. zpool add tank /dev/sdX with a bare disk welds a redundancy-less vdev into your pool of mirrors, permanently. Now that one consumer drive can take down everything, and the two mirrors you paid for protect nothing. The pool is exactly as strong as its weakest vdev.

Audit your real layout in ten seconds: zpool status indents the truth—vdevs (mirror-0, raidz1-0) at one level, member disks under them. A disk sitting at vdev indentation with no group above it is a single-disk vdev. If you find one under data you care about, that's a rebuild-the-pool conversation, not a someday conversation.