Filesystem choice for /home shapes the operational experience of a cPanel host more than most operators expect. Quota accuracy, snapshot capability, inode ceiling, and large-directory performance all depend on it. The choice is also nearly permanent — converting /home from one filesystem to another requires offlining accounts.
The trade-off
- ext4 — the default on most distributions. Mature, well understood, supports the journaled-quota system that cPanel relies on. Inode count is fixed at filesystem creation; running out of inodes requires reformatting. No snapshots without LVM underneath.
- XFS — better at very large filesystems and many small files. Dynamic inode allocation (no fixed ceiling). Strong concurrent metadata performance. Snapshots require LVM. cPanel supports XFS but the path is slightly less tested than ext4.
- ZFS — the most feature-rich. Native snapshots, compression, checksumming, send/receive replication. Higher RAM footprint (ARC eats memory aggressively by default). cPanel does not natively use ZFS for quota — you have to handle quota via ZFS native or stick to project quotas.
How to decide
Walk the workload:
- High account density with many small files (web shared hosting)? XFS or ext4. Both handle this well; XFS scales better past ~10 million inodes per filesystem.
- Need native snapshots for JetBackup integration? ZFS. The snapshot-based backup workflow is faster and more storage-efficient than rsync-style copies.
- Compliance regime requires checksumming for data integrity? ZFS. ext4 and XFS don’t checksum data blocks.
- Memory-constrained host (under 32 GB RAM)? ext4. ZFS ARC will eat all available RAM and fight the buffer cache.
- Need to grow filesystem online frequently? XFS or ZFS. ext4 can grow but the experience is rougher.
What to do
- Pick ext4 if you’re not sure. It’s the path of least surprise on cPanel.
- Pick XFS if you expect inode counts above 10 million per filesystem, or if you’re building dense shared hosting (200+ accounts per host).
- Pick ZFS only if you’ll actually use snapshots, compression, or send/receive — and only on hosts with at least 32 GB RAM dedicated to the host (not LVE-allocated to tenants).
- Enable quotas at mount time:
usrquota,grpquotafor ext4/XFS, ZFS native quotas if ZFS. Runquotacheck -avugafter enabling. - Track inode utilization, not just disk space:
df -i. Inode exhaustion looks like “disk full” butdfshows space.
For a deep dive on quota strategy, see the quota and inode limits guide. Stack Harbor specifies and operates these filesystems under cPanel/WHM management.