You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When building and running from the alpine:latest Docker image, the following error occurs:
zpool_latency_vdev_scrub_histo_seconds_bucket{name="tank",vdev="root",le="+Inf"} 14168517
zpool_latency_vdev_scrub_histo_seconds_sum{name="tank",vdev="root"} 0
zpool_latency_vdev_scrub_histo_seconds_count{name="tank",vdev="root"} 14168517
error: can't get vdev_trim_histo
I do not have any SSDs attached to this machine, so perhaps that's why it isn't working. When I remove the TRIM-related lines, the application runs to completion.
The text was updated successfully, but these errors were encountered:
This can happen if the runtime ZFS kernel module does not match the compiled header files.
Can you share the version of the ZFS kernel module: modinfo zfs | grep version ?
ok, trim support appears in ZFS version 0.8.0. So the binary must have been compiled in a
version 0.8.x or later system.
Ideally, the runtime is the same version of ZFS as compile time. If they are not the same,
then it is possible to cause zpool_prometheus to break for other incompatibility reasons.
That said, I think we can be a little bit smarter about backwards compatibility. I'll take a look
at it this week. Either way, there will need to be a recompilation of zpool_prometheus for
your container.
Long term, I plan to contribute zpool_prometheus into the OpenZFS mainline. Once that
happens there will always be a zpool_prometheus compiled to match the corresponding
ZFS kernel module.
When building and running from the
alpine:latest
Docker image, the following error occurs:I do not have any SSDs attached to this machine, so perhaps that's why it isn't working. When I remove the TRIM-related lines, the application runs to completion.
The text was updated successfully, but these errors were encountered: