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
OVH rented server | Scale i3
Distribution Name | Proxmox (debian 12)
Distribution Version | pve-manager/8.0.4/d258a813cfa6b390 (running kernel: 6.2.16-15-pve)
Kernel Version | 6.2.16-15-pve
Architecture | X86-64
OpenZFS Version |. zfs-2.1.13-pve1, zfs-kmod-2.1.13-pve1
Describe the problem you're observing
ZFS completely crashes when doing a zfs send/recv command (sometimes booting a VM can trigger the same reaction).
This makes zfs replication between servers hang and eventually crashes the zpool and takes the server down with it, making zfs completely unusable as a hypervisor backend.
I have 9 servers in this proxmox cluster and this message pops up only on the 2 most recently rented servers.
Never had an issue like this before where the whole server was rendered unusable.
Describe how to reproduce the problem
Clean install zfs via proxmox, zfs send a vm image (100GB+) to this server via replication, next I do a ZFS replication send to another healthy server in our cluster. Booting the VM mid-transfer somethimes triggers this behaviour, altough it's not required.
Might occure after 2MB transfered, might happen after 75GB, ...
Include any warning/errors/backtraces from the system logs
I was able to capture follow kernel messages via serial-over-LAN:
Compiled and installed zfs from the 2.2 master branch and this indeed fixes the issue.
Copied some data (100GB+) between the 2 Rapid sapphire lake servers and booted VM's without any issues now.
Will this fix be backported to 2.1? I don't know if proxmox will follow the 2.2 release schedule and provide these packages?
W.r.t. backporting: There are only minimal changes in the variable referenced in the changed line between 2.1.13 and master, so it should be relatively easy to backport when assembling the next ZFS 2.1 stable release – but I can send one too if that's preferred.
FWIW, in Proxmox VE the fix is shipped in proxmox-kernel-6.2.16-17-pve version 6.2.16-17 (or newer).
System information
OVH rented server | Scale i3
Distribution Name | Proxmox (debian 12)
Distribution Version | pve-manager/8.0.4/d258a813cfa6b390 (running kernel: 6.2.16-15-pve)
Kernel Version | 6.2.16-15-pve
Architecture | X86-64
OpenZFS Version |. zfs-2.1.13-pve1, zfs-kmod-2.1.13-pve1
Describe the problem you're observing
ZFS completely crashes when doing a zfs send/recv command (sometimes booting a VM can trigger the same reaction).
This makes zfs replication between servers hang and eventually crashes the zpool and takes the server down with it, making zfs completely unusable as a hypervisor backend.
I have 9 servers in this proxmox cluster and this message pops up only on the 2 most recently rented servers.
Never had an issue like this before where the whole server was rendered unusable.
Describe how to reproduce the problem
Clean install zfs via proxmox, zfs send a vm image (100GB+) to this server via replication, next I do a ZFS replication send to another healthy server in our cluster. Booting the VM mid-transfer somethimes triggers this behaviour, altough it's not required.
Might occure after 2MB transfered, might happen after 75GB, ...
Include any warning/errors/backtraces from the system logs
I was able to capture follow kernel messages via serial-over-LAN:
The text was updated successfully, but these errors were encountered: