The issue of created zpools not being imported on boot, due to a missing/partial/corrupt zpool.cache file is something which we see quite often reported in our various support-channels.
With PVE the issue was mitigated (and it did not show up so often), since pvestatd does activate all storages (which imports all referenced zpools). This does not hold for proxmox-backup (see the thread in our community forum [0]). After a short off-list discussion with Fabian (G.) the following patchset addresses the issue by adding 'zpool-import@.service' to our zfsonlinux repo and instantiating the template unit in the API paths where we create zpools (for storages or datastores) quickly tested on testsetups of mine (by adding a pool and then checking when it got imported according to the journal). [0]: https://forum.proxmox.com/threads/pbs-chunks-error-after-update.75467/ zfsonlinux: Stoiko Ivanov (1): Add systemd-unit for importing specific pools ...md-unit-for-importing-specific-pools.patch | 75 +++++++++++++++++++ debian/patches/series | 1 + debian/zfsutils-linux.install | 1 + 3 files changed, 77 insertions(+) create mode 100644 debian/patches/0008-Add-systemd-unit-for-importing-specific-pools.patch proxmox-backup: Stoiko Ivanov (1): api2/node/disks/zfs: instantiate import service src/api2/node/disks/zfs.rs | 5 +++++ 1 file changed, 5 insertions(+) pve-storage: Stoiko Ivanov (1): Disks: instantiate import unit for created zpool PVE/API2/Disks/ZFS.pm | 6 ++++++ 1 file changed, 6 insertions(+) -- 2.20.1 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
