Search results

Hi, in the end we think it was the Samsung EVO 870 disks and a bug they have with Linux. These disks are blacklisted. we have since replaced with Enterprise SSD and no longer have the problem.

anyone got this working yet?

this is now fixed under kernel 6.2.16-19

to be honest im suprised no one else has reported it on the forums :)

vmm0:t1:vcpu-0:Invalid VMCB Yep, this is a bug and exists in kernel 6, its still not fixed. Only work around is to boot kernel 5. Its a pain but has been around for a few months.

we have booted all nodes in 5.15.108-1 so far no issues but will see how it goes, we have left KSM enabled and not set the mitigations=off

been having this issue since upgrading to V8 from v7, mainly on Win VMs with large amount of RAM.

we are also seeing this.

i should also mention we have an NVMe pool, this is working fine. In summary 4 x nodes 128 GB Per node Proxmox 7.4-3 Kernel 5.15.104-1-pve 10Gb storage network 2 x 4TB SSD for ceph per node 1 x 1TB NVMe for ceph per node 1 x 1TB NVMe for local per node 1 x Ceph-ssd pool 1 x Ceph-NVMe pool

Hi, has anything changed with the latest build of Proxmox / Kernel that would of caused high disk latency with AMD Sata Controllers? We have a 4 node Ceph cluster with 2 x Samsung EVO 4TB 870s in each node , its been running great with fast read/writes for over 2 months, however we were made...

did you get to the bottom of this? i have the same issue, it was running fine, then over night we are seeing high latency across our SSD pool. 8 drives with high latency but its not consistent.

I don't think it can be the pbs server as when checking during backup its hardly doing anything. Is there a way to slow the backup down on the pve server?

i have been using snapshot mode anyway, but sadly this isnt working out. So as a test i have been using nas nfs backup using gzip, so far no issues. So it seem when using ZSTD the issue starts. Also with PBS, we cannot select a compression so i guess it is also using ZSTD.

its not one disk? The PBS server is on a 3 disk array. The issue is that the backup will seemingly run ok, then suddenly the writes drop to 0kb and the IO wait time and load increases significantly on the pve server. Originally we had a 2 disk stipe on the NAS server, we never had one issue...

Hi, did you get anywhere with this? we are also experiencing this issue. We have tried using PBS and also to the NAS itself on a seperate 2 disk stripe. the backups work ok, then all of a sudden IO delay jumps up and all VMs become unresponsive. We never had this issue on V6, it only seems to...

ah you are right, admin oversight, thanks for pointing that out

NAME AVAIL USED USEDSNAP USEDDS USEDREFRESERV USEDCHILD backupdata 5.31T 384K 0B 96K 0B 288K NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT backupdata 5.44T 384K 5.44T - - 0% 0%...

Hi, i just created a new backup server, created a new ZFS pool which is over 5TB in size. When i create a datastore its only using 194GB. Is there a way i can make the datastore larger? thanks Ian

Setting Async IO: threads and cache to Write back seems to have stablised it. We have had to do this on the HD even though its set to VirtoIO.

its a bit weird, we have a few other Windows VMs and they are not having this issue. The 2 Windows VMs in question are non production, the rest are production (luckily). I cant see anything that is different in the config. I will also add the ones that are working have IDE CD ROMs. Initially...