How to Configure and Manage ZFS Storage Pools and Datasets on Ubuntu Server

ZFS (Zettabyte File System) is an enterprise-grade file system and logical volume manager that provides unmatched data integrity verification, copy-on-write transactional architecture, native snapshotting, and built-in software RAID redundancy. On Ubuntu Server, OpenZFS is supported directly through official kernel modules, allowing administrators to pool physical drives, eliminate silent bit rot, and manage storage with unprecedented efficiency.

Installing OpenZFS on Ubuntu Server

OpenZFS utilities are packaged in the default Ubuntu Universe and Main repositories. Update your package database and install the core userland binaries and DKMS modules:

sudo apt update
sudo apt install zfsutils-linux -y

Once installed, verify that the ZFS kernel module is loaded properly into the operating system:

lsmod | grep zfs
zfs --version

Creating ZFS Storage Pools (zpool)

ZFS pools aggregate physical block devices (HDDs or NVMe SSDs) into a unified storage space. Always identify drives using their persistent device IDs located in /dev/disk/by-id/ rather than transient names like /dev/sdb.

Pool Layout	Minimum Disks	Fault Tolerance Level	Storage Efficiency
Stripe	1	None (Zero drive failure tolerance).	100% of raw disk space.
Mirror	2	1 drive per mirror vdev.	50% (identical duplicate copy).
RAID-Z1	3	1 drive failure tolerated (similar to RAID 5).	(N – 1) disks usable.
RAID-Z2	4	2 simultaneous drive failures tolerated.	(N – 2) disks usable.

To create a resilient mirrored pool named datapool using persistent drive IDs:

sudo zpool create -f -o ashift=12 datapool mirror   /dev/disk/by-id/ata-WDC_WD40EFRX_DISK1   /dev/disk/by-id/ata-WDC_WD40EFRX_DISK2

Note: Setting ashift=12 aligns disk blocks to modern 4KB physical sectors, maximizing I/O performance.

Creating Datasets and Enabling Transparent Compression

Unlike traditional partitions, ZFS datasets behave like dynamically resizable filesystems that share storage from the common pool. Enabling LZ4 compression dramatically accelerates read/write performance while saving disk space:

# Enable LZ4 compression globally on the pool
sudo zfs set compression=lz4 datapool

# Create dedicated datasets for distinct workloads
sudo zfs create datapool/shared_docs
sudo zfs create datapool/backups

# Verify compression ratios across all datasets
zfs get compression,compressratio datapool

Managing Atomic Snapshots and Instant Rollbacks

Because ZFS uses a copy-on-write architecture, creating a snapshot is instantaneous, read-only, and consumes zero additional disk space until underlying files are modified or deleted:

# Take an immediate snapshot of the shared_docs dataset
sudo zfs snapshot datapool/shared_docs@snapshot_baseline

# List all existing snapshots
zfs list -t snapshot

# Roll back the dataset to the snapshot state if files are corrupted
sudo zfs rollback datapool/shared_docs@snapshot_baseline

Monitoring Pool Health and Scrubbing

To detect and silently repair bit rot or checksum mismatches across disk sectors, schedule regular ZFS scrubs:

# Initiate a background data integrity scrub
sudo zpool scrub datapool

# Check real-time scrub progress and pool health
zpool status datapool

If ZFS identifies corrupted blocks during a scrub, it automatically reconstructs the clean data using parity or mirrored copies without taking the pool offline.