I'm back at -5 and the problem vanished .
So basically the problem appeared in -6 (as per Galaxis) , is still there in -8, I was just a bit late in the game.
If it's a new kernel feature and not the sign of the disks getting crazy, it sure...
Hey! Sorry, I completely missed your reply, and I apologize for getting back to you so late.
Unfortunately, I'm primarily a macOS developer and don't have a Windows machine. Also, I have to admit that C# isn't really my favorite language to work...
Since @weppa writes it was still fine in -5 (which I skipped coming from -4), and the effect first showed up for me in -6, something must have happened between those two versions.
Thanks @Neobin !
In the meantime
proxmox-boot-tool kernel pin 7.0.14-5-pve
proxmox-boot-tool refresh
UPDATE : I can confirm the problem DISAPPEARS with kernel 7.0.14-5
So it's specific to kernels after this one.
Since @weppa writes it was still fine in -5 (which I skipped coming from -4), and the effect first showed up for me in -6, something must have happened between those two versions.
I agree that GitOps, Ansible, sudo, and similar tooling are all valid operational approaches. My point isn't that there are no workarounds. My point is that the supported first-party GUI still lacks an enterprise identity model for host lifecycle...
Well, you can limit the sudo priviledge by specifying the exact commands that should be capable to run.
(e.g. %test ALL=(ALL:ALL) /usr/bin/apt update, /usr/bin/apt upgrade -y) and sudo logs all actions to journalctl
If you like to try out a...
Have you checked this https://forum.proxmox.com/threads/advice-needed-upgrade-pve-8-to-9-using-systemd-boot-with-zfs-rpool-uefi-and-no-secure-boot.181956/
Thanks,
lsblk -f
shows a UUID for the EFI System Partition, so I don't think this solution applies to my case.
I also don't want to reformat the ESP without knowing that it is actually the problem.
Thanks for this suggestion. I will need to run this tonight during a quieter period since i do have production running. Would a smaller sample, such as 32 GiB, still provide a useful comparison between TrueNAS, PVE01 (node 1), and PVE99 (node 2)...
I think the main issue with adding such a feature to the API would be that anybody who can do system upgrades basically gets "root" powers. So if your compilance requirements are that you need to limit the potential breakage done by a single...
You mean as in paying for the subscriptions? which every enterprise I manage have deployed PVE on does? Love how this comes back to "you want a feature then contribute" when that is not even the issue here. If you mean open a ticket, or file a...
If your system have lots of free RAM, but: 1. swap is full, 2. ARC lower than your expectation and 3. have an active dataset with >=256k recordsize. You might be affected by this bug.
You can try stop the workload on the dataset to see if...
Thank you. got my MS-A2 9955hx downgraded with your file from 1.03 to 1.02 and PCIE-Passthrou works again unter proxmox.
Many many thanks
PS: i even reportet the problem in detail to minisforum.
ZFS don't like nfs default export sync behavior which can be a bit alleviated with a slog device.
Your 25Gb node1 still shows more I/O pressure as data would come faster as on the other and so normally you see the higher pressure there.
Download...
I have been seeing this issue for years and recently I finally figured it out: https://github.com/openzfs/zfs/issues/18893
Before this bug is fixed do not use recordsize that is >= 256k.