Recent content by Andrii.B

This bug occurs even if it’s only uses 50% of RAM (221 GB of 512 GB).

There is a similar and newer topic here. This problem occurs when creating a backup with big disk space. It depends with ballooning. I'm still investigating how to resolve it but it seems to me, it's necessary to disable ballooning on VM.

It doesn't help.

I can't say that it works bad, but the graphs show different things than on LVM.

Yes, I use it on all my nodes, except NVMe. As for ZFS, I use Micron 7500 Pro. I'm testing a new configuration with ZFS, NVMe, instead of Enterprise SSD in HW Raid.

The same issue I see on VMs. I limited a drive performance on VM (iops, MB/s). There is 3% IO Pressure Stall on ZFS VM and 0% IO Pressure Stall on LVM VM. It seems IO Pressure Stall doesn't work correctly with LVM or hardware raid.

I don't feel it, of course. But it's strange, because it's there is less writes on ZFS and iostat show the following: LVM: AVG 1000 r/s, 25 MB/s, 2 %rrqm, 0.4 r_await, 500 w/s, 7 MB/s, 2 %wrqm, 0.05 w_await, 10 %util ZFS: AVG 100 r/s, 1.2 MB/s, 0 %rrqm, 0.1 r_await, 150 w/s, 7 MB/s, 0 %wrqm...

Anyone can me explain why the IO pressure stall always display average 0.1% on ZFS on 4x NVMe, but LVM on hardware raid with SSD usually display zero for all time, except rare bursts when VMs is cloning?

I understand. Thanks a lot!

I have no newer versions yet. There isn't updated. I'm using the enterprise repositories.

But I am.

These packages aren't available on my side yet.

I don't know how you checked it, but on pve 9.0.6 it still doesn't work.

Thank you. Can you tell me when this update will be published to get this update?

A new version doesn't return graph images using /api2/json/nodes/{node}/qemu/{vmid}/rrd?timeframe=day&ds=cpu "image":null