We uploaded a bunch of kernels with newer ZFS versions yesterday:
The 5.13 based kernel is still opt-in only, it will be the one we default to in Proxmox VE 7.1 (planned for 2021/Q4).
- Proxmox VE 6.4 (oldstable):
- pve-kernel-5.4.143-1-pve (
5.4.143-1
) with ZFS2.0.6
- pve-kernel-5.11.22-5-pve (
5.11.22-10~bpo10+1
) with ZFS2.0.6
- Proxmox VE 7.0 (stable):
- pve-kernel-5.11.22-5-pve (
5.11.22-10
) with ZFS2.0.6
- pve-kernel-5.13.14-1-pve (
5.13.14-1
) with ZFS2.1.1
That means that 5.11 is slowly on its way out, and that's why we did not bother with updating the ZFS module there to the 2.1 series.
To test ZFS 2.1 and the 5.13 based kernel add the pvetest repo and do:
Bash:apt update apt full-upgrade apt install pve-kernel-5.13 # -> reboot
Yes, pretty sure, I did the buildAre you sure that pve-kernel 5.11 test ships with ZFS 2.0.6?
pve-kernel-5.13
package you'll get 2.1.1 user-space but 2.0.6 kernel module.zfs -V
, for example:zfs -V
zfs-2.1.1-pve1
zfs-kmod-2.0.6-pve1
uname -a
Linux prod2 5.11.22-5-pve #1 SMP PVE 5.11.22-10 (Tue, 28 Sep 2021 08:15:41 +0200) x86_64 GNU/Linux
zfs -V
zfs-2.1.1-pve1
zfs-kmod-2.1.1-pve1
uname -a
Linux prod1 5.13.14-1-pve #1 SMP PVE 5.13.14-1 (Tue, 28 Sep 2021 06:16:44 +0200) x86_64 GNU/Linux
Yes, pretty sure, I did the build
https://git.proxmox.com/?p=pve-kernel.git;a=shortlog;h=refs/heads/pve-kernel-5.11
The thing is that we do not divide user-space tools per major version in separate packages as they're backward compatible anyway. So, if you just update but do not install thepve-kernel-5.13
package you'll get 2.1.1 user-space but 2.0.6 kernel module.
You can check both, user and kernel version withzfs -V
, for example:
Bash:zfs -V zfs-2.1.1-pve1 zfs-kmod-2.0.6-pve1 uname -a Linux prod2 5.11.22-5-pve #1 SMP PVE 5.11.22-10 (Tue, 28 Sep 2021 08:15:41 +0200) x86_64 GNU/Linux
And for 5.13 based kernel it looks like:
Bash:zfs -V zfs-2.1.1-pve1 zfs-kmod-2.1.1-pve1 uname -a Linux prod1 5.13.14-1-pve #1 SMP PVE 5.13.14-1 (Tue, 28 Sep 2021 06:16:44 +0200) x86_64 GNU/Linux
Thanks for the @mention, but it wouldnt do me any good now since I cant reform a pool retroactively...@alexskysilk If that is still relevant for you, I just discovered ZFS 2.1 in the pvetest repository.View attachment 29872
Backward compatible, sure. You naturally cannot use newer features the user-space tools would know already about (e.g., draid).Are they (user-space 2.1.1 and kernel 2.0.6 100% compatible?
*sad ZFS noises*In the future I will no longer use zfs anyway
Proxmox VE 6.4 is in bug & security fix only mode since the release of Proxmox VE 7.0, so we won't take in new feature releases of upstream project, iow. PVE 6.4 will stay on ZFS 2.0.x.I am actually glad you kept 6.4 test kernel on 2.0.6, 2.0.6 probably less risky than 2.1 at the moment.
As mentioned, it's only on theI just updated and it pulled down 5.11.22-4 not 5.11.22-5 and zfs still on 2.0.5..
pvetest
repository at time of writing, it will move to no-subscription in a bit and only later to the enterprise repository, at least if no issue pops up.Do you plan to update 5.11 kernel in pve 6.xx version to latest ZFS (2.0.7)? User-space tools was updated to 2.0.7 recently.Proxmox VE 6.4 is in bug & security fix only mode since the release of Proxmox VE 7.0, so we won't take in new feature releases of upstream project, iow. PVE 6.4 will stay on ZFS 2.0.x.
As mentioned, it's only on thepvetest
repository at time of writing, it will move to no-subscription in a bit and only later to the enterprise repository, at least if no issue pops up.
No, 5.11 won't get any update anymore, you can update to 7.x if you require a newer kernel:Do you plan to update 5.11 kernel in pve 6.xx version to latest ZFS (2.0.7)?
Those can manager the slightly older 5.11 kernel module just fine though.User-space tools was updated to 2.0.7 recently.