The tmpfs mount workaround works, I added it to fstab to make it a permanent change. Combined with a swap disk I'm not worried about running out of memory.
Opt-in Linux 6.1 Kernel for Proxmox VE 7.x available
- Thread starter t.lamprecht
- Start date
Thank you very much for your help with this. Setting /tmp as a tmpfs mount does, indeed, seem to have resolved this issue on my systems.
Go to the shell in the Proxmox GUI and type 'vi /etc/fstab' and add the following line:
Code:
tmpfs /tmp tmpfs defaults 0 0The size is dynamic and the kernel can swap it out if needed so it's not going to steal memory when it doesn't need to.
https://www.kernel.org/doc/html/latest/filesystems/tmpfs.html
There are ZFS updates for Proxmox no-subscription, including a new 5.15 kernel version with newer ZFS support, but no 6.1 kernel version updates. I wonder if dist-upgrading would break a Proxmox VE running with kernel 6.1.
EDIT: pve-kernel-5.15.83-1-pve explicitly mentions support for the ZFS 2.1.7-pve1 updates (from 2.1.6-pve1), but I can't see the kernel 6.1 change log as easily in the GUI.
EDIT: pve-kernel-5.15.83-1-pve explicitly mentions support for the ZFS 2.1.7-pve1 updates (from 2.1.6-pve1), but I can't see the kernel 6.1 change log as easily in the GUI.
Last edited:
* which zfsutils-linux version do you currently run, and which is about to get updated?
* the 6.1 kernel already ships with ZFS 2.1.7 kernel part
in general AFAIR zfs userspace utils and kernel version mismatches (e.g. 2.1.6 userspace and 2.1.7 kernel or the other way around) are not a cause of problems (or have not been until now in my experience)
Will there be a posting on this thread when this kernel is available on the enterprise repository?
Yes, we'll update this thread then. But we'll wait until the ZFS tmpfile issue got resolved before moving it on.
Please be aware of the latest kernel 5.15 serious security flaw: https://www.zdnet.com/article/patch-now-serious-linux-kernel-security-hole-uncovered/
I've been using the Edge kernels since months on several machines without issue - Thankful for the 6.1 release!!
Happy Holidays!
I've been using the Edge kernels since months on several machines without issue - Thankful for the 6.1 release!!
Happy Holidays!
this is a non-issue.Please be aware of the latest kernel 5.15 serious security flaw: https://www.zdnet.com/article/patch-now-serious-linux-kernel-security-hole-uncovered/
I've been using the Edge kernels since months on several machines without issue - Thankful for the 6.1 release!!
Happy Holidays!
ksmb is not active, and it was patched a long time ago in 5.15.61.
Proxmox is now at 5.15.83 (at least with non-subscription repo)
Please be aware of the latest kernel 5.15 serious security flaw: https://www.zdnet.com/article/patch-now-serious-linux-kernel-security-hole-uncovered/
I've been using the Edge kernels since months on several machines without issue - Thankful for the 6.1 release!!
Happy Holidays!
I wouldn't be too concerned about it if you are not using ksmbd (in-kernel smb server, userspace smb implementation - samba - is not affected). Also it is only of concern to those who do use ksmbd with many random users.
Yeah the price we pay for having bleeding edge tech. There's some big strides being made in the Asus sensors department and wanted to test against my z690 proart since it shares the same chip as boards on the latest supported list. Problem is we're about 8 weeks or more away from seeing this in mainline.
You need to use
pve-headers-6.1.0-1-pve for Proxmox VE. It works fine with building the vendor-reset module. It comes automatically with pve-headers-6.1.
Following up on this, as I have not seen any replies: I did some testing and noticed that pve-kernel-6.1 does not expose an EUI identifier for one of my NVMe devices, and therefore its WWID changes too (which is supposed to be unique and stable?) compared to default pve-kernel-5.15 (which shows an
eui for both of them!):
Code:
» ls -l /sys/block/nvme*/{wwid,eui}
-r--r--r-- 1 root root 4.0K Dec 28 18:02 /sys/block/nvme0n1/eui
-r--r--r-- 1 root root 4.0K Dec 28 18:00 /sys/block/nvme0n1/wwid
-r--r--r-- 1 root root 4.0K Dec 28 18:00 /sys/block/nvme1n1/wwid
» cat /sys/block/nvme0n1/wwid /sys/block/nvme1n1/wwid
eui.0026b7683b8e8485
nvme.1987-504e593039323030303033373930313030343131-504e592043533330333020323530474220535344-00000001For sake of testing, I also installed pve-kernel-5.19 and to my suprise the exact same issue already happens with 5.19!
Is someone else seeing this with either 5.19 or 6.1 (i.e. missing
/sys/block/nvme*/eui and/or inconsistent wwid)?Regards
Last edited: