What is a Zpool?
What Is a Zpool?
A zpool is a ZFS storage pool. It is built from one or more virtual devices, commonly called VDEVs. Those VDEVs are in turn constructed from physical storage devices such as hard drives or SSDs.
Instead of assigning individual drives directly to separate file systems, ZFS combines storage resources into a pool. ZFS file systems and other datasets can then consume capacity from that shared pool.
Drives → VDEVs → Zpool → Datasets
One of the most important concepts in ZFS is understanding how physical drives, VDEVs and the storage pool relate to one another.
Physical Drives
HDDs, SSDs or other supported block storage devices provide the physical capacity used by ZFS.
VDEVs
Drives are organized into virtual devices such as mirrors or RAIDZ groups. The VDEV determines important redundancy and performance characteristics.
Zpool
One or more VDEVs are combined into the ZFS storage pool, providing the storage resources available to ZFS.
Datasets
File systems, volumes and other datasets consume storage from the capacity provided by the pool.
A Zpool Is Built From VDEVs
The VDEV is one of the most important building blocks in ZFS. A pool may contain a single VDEV or multiple VDEVs, and each VDEV may itself contain multiple physical drives.
This distinction matters because redundancy exists primarily within the individual VDEVs. Adding multiple VDEVs increases the pool's total capacity and can improve aggregate performance, but it does not make one VDEV protect another VDEV.
How Can a Zpool Be Configured?
A pool can be constructed from different VDEV layouts. The appropriate design depends on capacity, performance, redundancy requirements and the workload.
Single Mirror VDEV
A simple pool could contain two drives configured as one mirrored VDEV.
Single RAIDZ2 VDEV
A larger pool might use several drives together in a RAIDZ2 VDEV for double-parity protection.
Multiple Mirror VDEVs
Multiple mirrored VDEVs can be combined in one pool, increasing capacity and distributing I/O across VDEVs.
Losing a Top-Level Data VDEV Can Lose the Pool
The redundancy of each top-level data VDEV is critical. If a top-level data VDEV becomes unavailable beyond the protection provided by its layout, the pool can become unavailable and data can be lost.
For example, adding an unprotected single-disk data VDEV to an otherwise redundant pool can introduce a single point of failure. Pool design should therefore be planned around the failure tolerance of every data VDEV rather than considering only the total number of drives in the pool.
How Is Zpool Capacity Determined?
Pool capacity depends on the number and size of the drives, the VDEV layout, redundancy overhead and other ZFS storage requirements. Mirroring and RAIDZ use some raw drive capacity to provide redundancy.
VDEV Layout Affects Zpool Performance
Pool performance depends on more than the total number of drives. VDEV topology, drive performance, workload, record sizes, available memory and other ZFS configuration choices can all influence results.
Is a Zpool the Same as a RAID Array?
Not exactly. Both approaches can combine multiple storage devices, but ZFS integrates storage pooling with filesystem-level features and data-integrity mechanisms. Redundancy in a ZFS pool is determined by its VDEV topology, such as mirrors or RAIDZ.
Conventional RAID commonly presents a logical block device to a separate filesystem. ZFS instead manages storage and filesystem functionality as part of an integrated architecture.
Choosing Drives for a Zpool
ZFS can be deployed across many storage configurations, but drive characteristics still matter. Capacity, endurance, latency, interface, workload rating and failure behavior should be considered when selecting storage devices.
A Redundant Zpool Is Not a Backup
Mirrors and RAIDZ can help a pool remain available through supported drive failures, but redundancy does not protect against every form of data loss. Accidental deletion, application errors, administrative mistakes, malware, catastrophic hardware damage and site-level failures can still affect data.
Important data should be protected by an independent backup strategy appropriate for the environment.
Zpool FAQ
What does zpool mean?
Zpool refers to a ZFS storage pool composed of one or more VDEVs.
What is the difference between a zpool and a VDEV?
A VDEV is a storage building block made from one or more devices. A zpool is built from one or more VDEVs.
Can a zpool contain multiple VDEVs?
Yes. A ZFS storage pool can contain multiple top-level VDEVs.
Is RAIDZ a zpool?
No. RAIDZ describes a redundant VDEV layout. One or more VDEVs are used to build a ZFS pool.
Can I use SSDs in a zpool?
Yes. ZFS pools can use SSDs and other supported block storage devices, subject to the platform and implementation.
Can losing one VDEV destroy a pool?
If a top-level data VDEV is lost beyond its redundancy tolerance, the pool can become unavailable and data may be lost.
Is a mirrored zpool a backup?
No. Mirroring provides storage redundancy but does not replace an independent backup strategy.
Does adding more VDEVs improve performance?
Multiple data VDEVs can increase aggregate I/O capability, although actual performance depends on topology, devices, workload and ZFS configuration.