Search results

I used a snapshot on an LXC (Home Assistant Core) and it was very quick with no delays. Ditto for a larger W 2102 VM. I appreciate that's not immediately useful for you. Good luck!

A shame - mine is still working fine after several days of typical use on both nodes. That's no use to you I know and I guess the problem is complex.

It will be indeed be interesting to see what other people get. My rig has no SSDs, decent quality SATA drives and showed the issue consistently since the availability of the 6.5 kernel. My workload is light, but quite consistent and with a typical workload I had IO loads of 40-60% whereas now...

Excellent news. I think it's the ZFS release that's vital as I've used several 6.8 kernels where the problem remained.

An update from me which looks at first sight to be very positive. I upgraded to the proxmox Linux 6.8.12-2-pve which *also* includes zfs 2.2.6. This worked fine with my 6.2 kernel and then I rebooted to use 6.8.12-2 and after several hours of normal usage, I am seeing no significant IO delays...

My 2 NAS boxes are both HP Microservers and no further BIOS updates are available. I still see the issue with the latest 6.8 kernels and I am not using any Windows VMs, nor SSDs. My 6.2 kernel is chugging along nicely :-) without the issue on the same boxes

I don't use SSD at all. These are older style spinning rust mirrors. I agree that it would seem odd that moving from 6.2 or 6.8 with the same version of ZFS introduces this increase in IO delay, but that it what I see. Ho hum

Thanks for that reminder - I have my MAX arc a bit higher than yours and I'm happy with the performance. The cluster doesn't have a high load either CPU or IO. Maybe when the next kernel or ZFS version comes out I'll review the ZFS settings again.

The services pve-cluster, corosync, pvestatd, pveproxy and pvedaemon were all restarted which I know is very heavy handed but which seemed to be what other people have used to kick the gui into life again. But not for me :) The only weird thing I can think of with ZFS is that from time to...

Yes some progress with my non-SSD based system. I ran a 6.5 kernel very well for 2-3 days without any instances of high IO delays, but then one node would no longer display the GUI details for the VMs and LXCs. I was just seeing ? and timeout messages on the GUI. The other node was fine. The...

Interestingly as a test I moved back to a 6.5 kernel on both nodes, 6.5.13-5-pve and the iodelay is fine once again. My guess is that when I first upgraded to a 6.5 kernel ages ago, there was some other factor which combined with a 6.5 kernel resulted in the high IO delays. Perhaps ZFS...

I just toggle between the two kernels with pve-boot-tool. The upgrades to proxmox 8.2 were done ages ago, so no upgrade was involved in this switching. My default kernel is 6.2 and I then use sudo proxmox-boot-tool kernel pin 6.8.8-2-pve --next-boot and then rebooting the server. I've...

On my particular system the workloads with a 6.2 kernel are the same as with the same system running a 6.8 kernel. But the IO delays are much higher with 6.8.

Again just to emphasize that while I'm using ZFS for boot and data pools, I'm not using SSD. The issue (for me) was present the first time I tried 6.5 and also occurs with 6.8. I suspect that if there were to be a solution for my rig, that same solution would work for people with SSD drives too.

If it helps, I'm not using SSD on my old but servicable home lab. All spinning rust, but the issue is easy for me to reproduce by just doing a one off reboot into (say) 6.8. The io delays goes from its typical 1-3% up to 40-50 for as long as I leave it running. If I reboot back to the older...

I was running 6.2 as that was the standard proxmox kernel back then (sorry no exact date), but when the standard kernel moved to 6.5 I saw the problem and reverted back. Ditto on 6.8.x

I use the latest ZFS available on the non-production repositories and the problem persists. I think it's a kernel issue as 6.2 is fine, but 6.5 and 6.8 both show the same high IO for the same work.

I have much the same issue with both my nodes in a cluster, but I'm not using SSD, just plain mirrored spinning disks. I see high IO delay with both 6.8 and 6.5 kernel, but If I flick back to kernel 6.2, all is well.

Aha! It turns out that the directory step-ca provides for ACME is something along the lines of https://xxxxxxxx/acme/ACME/directory and not the base CA connection. Once I used that, all was well. My bad. Perhaps soemone else using step-ca might find the hint useful.

Sure no problem. I've not shown the actual site name, but it was correct when I ran the command. root@pvetest:~# pvesh get /cluster/acme/meta --directory "https://xxxxxxx" --output-format json-pretty Error: GET to https://xxxxxxxxx 404 page not found