How quickly does proxmox update zfs packages?

[Clete2]

We are on 2.1.7 but 2.1.8 has a critical fix that I need. 2.1.9 was released tonight. How frequently does proxmox (no subscription) update zfs packages?

 

[psyyo]

if it's a critical fix you absolutely need - why not just manually add those repos and upgrade?

 

[Clete2]

if it's a critical fix you absolutely need - why not just manually add those repos and upgrade?

I should’ve said it differently. It’s a fox for a panic during send and receive. I’ve paused my daily send backups due to the panic. So it’s more that I can’t backup my file system while on 2.1.7. I’m trying to decide if I should pull from Sid or just wait for proxmox to update.

 

[LnxBil]

I should’ve said it differently. It’s a fox for a panic during send and receive. I’ve paused my daily send backups due to the panic. So it’s more that I can’t backup my file system while on 2.1.7. I’m trying to decide if I should pull from Sid or just wait for proxmox to update.

ZFS in PVE is part of the pve-kernel, so you cannot (easily) replace the ZFS.

We are on 2.1.7 but 2.1.8 has a critical fix that I need. 2.1.9 was released tonight. How frequently does proxmox (no subscription) update zfs packages?

It's on its way.

 

[Clete2]

I assumed I could install the upstream Debian Sid packages to upgrade and that would build the kernel modules. Not as easy as that in proxmox?

 

[Stoiko Ivanov]

for completeness sake the patch was renewed to ZFS 2.1.9:
https://lists.proxmox.com/pipermail/pve-devel/2023-January/055592.html

assumed I could install the upstream Debian Sid packages to upgrade and that would build the kernel modules. Not as easy as that in proxmox?

I would recommend against mixing dkms modules (as shipped by upstream Debian), with the ones directly shipped in the kernel - mostly because it causes confusion and can lead to incompatibilites (although I would guess that should not happen too often as the userspace utils work quite well with different/older kernel modules in my experience)
One further point is that this is not supported from our side (and you have rather few users with such a setup that could help with issues)

Else - depending on which fix you need - and if the issue was recently introduced - you can go back to a kernel which does not have the issue (although that comes with the risk of potentially running a kernel with known vulnerabilities)