root@vmx02:~# uname -a Linux vmx02 4.13.16-2-pve #1 SMP PVE 4.13.16-47 (Mon, 9 Apr 2018 09:58:12 +0200) x86_64 GNU/Linux root@vmx02:~# apt-cache policy zfs-initramfs zfs-initramfs: Installed: 0.7.7-pve1~bpo9 Candidate: 0.7.7-pve1~bpo9 Version table: *** 0.7.7-pve1~bpo9 500 500 http://download.proxmox.com/debian/pve stretch/pve-no-subscription amd64 Packages 100 /var/lib/dpkg/status
I am now on:
and the issue with z_null_int seems to be gone. Now I can start doing performance testing Not sure though if it was the kernel, zfs or bothCode:
root@vmx02:~# uname -a Linux vmx02 4.13.16-2-pve #1 SMP PVE 4.13.16-47 (Mon, 9 Apr 2018 09:58:12 +0200) x86_64 GNU/Linux
I just want to add that I needed upgrade to 4.13.16-2-pve for the 0.7.7 fix to work.
Pure ZOL upgrade didn't work until after kernel upgrade to the latest. Even relatively new 4.13.13-6-pve kernel didn't work.
Thanx Proxmox team for delivering the fix.
You probably shall document it somewhere. I believe the "normal" ZFS implementation relies on DKMS mechanism, but it is not the case with Proxmox.
Particularly in my case, I was very confused when "dmesg | grep ZFS" returned 0.7.6, while 0.7.7 was actually installed. Now I understand the reason.