Then just tune the dataset for a general data storage device. 128K cluster size.
But yeah if you were doing databases and stuff or storing big files id say tweak it
Big files 1 MiB is a good spot (movies media)
Databases really prefer 16K from what ive found performance wise… Postgresql is finniky and likes 8k
VMs and QCOW2 files use cluster_size=64K
If you’re using a ZVOL as your VM’s storage back end, you should be aware that the same issues apply to its volblocksize tunable, which defaults to 8KiB. This is ideal or near-ideal for PostgreSQL, but a very bad choice for nearly any other workload.
Which distribution do you use. If your distribution does not package ZFS you either need to install it via a kernel module that builds ZFS for each new kernel that you install or you need to add a third party repository with prebuild packages. Those packages however always require the according kernel version.
Usually with the later case, either the kernel or the ZFS packages are handles specially from the package manager. So either the kernel, the ZFS package or both are excluded from updating.
Maybe something along those lines is happening here too. ZFS seems to have special protection in the package manager to not be changed. You should look into you package manager configuration if ZFS is excluded there and maybe you’d find a comment why that is. Without knowing which distribution we are talking about and how you installed ZFS I can’t tell more.
Edit: crap sorry, I just realized that post was from 10 days ago … were you able to resolve it?
I still have flashbacks when I remember my first experiences with water cooling and how I nearly ruined a perfectly fine computer. I still want pictures when finished though … tyvm.
That was how I learned water doesn’t kill electronics. It’s the stuff in the water which kills electronics. I knew that before I knew the reason why. I guess you call that watercooling bro-science.