Currently we have some troubles with High IO delay on almost any 'heavy' write on the VM. Our Proxmox is currently installed on Crucial MX500 with ZFS RAID 1. I was searching on the web and I saw that this could happen because of these disks can't handle much IOPS for VM Hosting.
On a few of our VMs we see the following behaviour when a backup runs.
The backup started at 05:00:02
From the outside the VM seems fine (proxmox summary page), but when the backup started the OS changed the disk into read-only mode
Oct 25 05:00:57 *******-SQL-02 kernel: [5294216.466540]...
ich habe mich nach meinem letzten Beitrag hier nun dazu entschieden zum rumspielen erstmal einfach so einen neuen Host aufzusetzen. Allerdings ist mir aufgefallen, dass das neue System permanent einen I/O-Delay anzeigt, selbst wenn gar keine VMs laufen. Wenn ich jetzt zB eine Windows VM laufen...
I am encountering some problems making backups on many servers running ZFS.
The PVE cluster is made of 4 nodes, every node have a ZFS mirror pool on 2 NVMe SSD drives and a full backup is made once per week at 00:30 on different days per each node:
Every time a backup is started I see...
Back from ESXi-land with another valuable question, well two in fact. The question in the title is about measuring CPU resource usage in more detail, for example in Proxmox I love that there is an oi-delay counter.
How would one go about measuring something like...