Files
nixpkgs/nixos/doc/manual/administration/zfs-state.section.md
Dark Steveneq 646b892680
Some checks failed
Periodic Merges (6h) / master → staging-nixos (push) Failing after 12m50s
Periodic Merges (6h) / master → staging-next (push) Failing after 12m54s
Periodic Merges (24h) / merge-base(master,staging) → haskell-updates (push) Failing after 11m54s
Periodic Merges (6h) / staging-next → staging (push) Failing after 12m13s
Periodic Merges (24h) / staging-next-25.05 → staging-25.05 (push) Failing after 13m24s
Periodic Merges (24h) / release-25.05 → staging-next-25.05 (push) Failing after 14m28s
push sheeet
2025-10-09 14:15:47 +02:00

821 B

ZFS

When using ZFS, /etc/zfs/zpool.cache should be persistent (or a symlink to a persistent location) as it is the default value for the cachefile property.

This cachefile is used on system startup to discover ZFS pools, so ZFS pools holding the rootfs and/or early-boot datasets such as /nix can be set to cachefile=none.

In principle, if there are no other pools attached to the system, zpool.cache does not need to be persisted; it is however strongly recommended to persist it, in case additional pools are added later on, temporarily or permanently:

While mishandling the cachefile does not lead to data loss by itself, it may cause zpools not to be imported during boot, and services may then write to a location where a dataset was expected to be mounted.