and an entry for the corrupted cachefile problem which keeps showing up in forum posts.
Signed-off-by: Oguz Bektas <o.bek...@proxmox.com> --- local-zfs.adoc | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/local-zfs.adoc b/local-zfs.adoc index 5cce677..c516db8 100644 --- a/local-zfs.adoc +++ b/local-zfs.adoc @@ -551,3 +551,32 @@ in the pool will opt in for small file blocks). ---- # zfs set special_small_blocks=0 <pool>/<filesystem> ---- + +[[zfs_troubleshooting]] +Troubleshooting +~~~~~~~~~~~~~~~ + +.Corrupted cachefile + +In case of a corrupted ZFS cachefile, some volumes may not be mounted during +boot until mounted manually later. + +For each pool, run: + +---- +# zpool set cachefile=/etc/zfs/zpool.cache POOLNAME +---- + +and afterwards update the `initramfs` by running: + +---- +# update-initramfs -u -k all +---- + +and finally reboot your node. + +Sometimes the ZFS cachefile can get corrupted, and `zfs-import-cache.service` +doesn't import the pools that aren't present in the cachefile. + +Another workaround to this problem is enabling the `zfs-import-scan.service`, +which searches and imports pools via device scanning (usually slower). -- 2.20.1 _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel