I noticed that zfs.ko got loaded unexpectedly on a few small systems I maintain, which don't run ZFS but only have UFS filesystems. Turned out that btop executed "zpool list" unconditionally to find out if there are any ZFS pools available. This caused zfs.ko to be loaded, which in turn causes a "zfskern" process to spike all cpu cores at 100% for about 10 seconds. I was discussing this with @nimaje on #freebsd on Libera and decided to file a bug. Our thinking was that probably, zpool and/or other zfs utilities should not auto-load zfs.ko at all.
Upstream bug in btop about (indirectly) causing zfs.ko to be loaded because of unconditionally executing zpool list: https://github.com/aristocratos/btop/issues/515
From GitHub: > FreeBSD Os release version: 12.4-RELEASE-p1
This idea makes sense to me. After all, if zfs.ko isn't already loaded, then there won't be any pools to list. However, I think that "zpool import" and "zpool create" should still be able to load the module. You should file a bug at https://github.com/openzfs/zfs .
any updates on this? I don't see any issue/pull requests on https://github.com/openzfs/zfs relating to it