Search results

Just joining an existing cluster already enables background services which rely on high speed & reliable network connections

As @sb-jw mentioned it would be good to know which hardware you use in your cluster and network.

You might want to use SR-IOV and pass the VF to your VM? According to Intels ARK database it should be possible.

My fstab mounts work just with spaces but without tabs. If it's a hardware RAID controller with no other usage then VM disks you might want to think about PVE built-in LVM-thin pools. They do the mounting "magic" automatically.

What is /dev/sdd for a drive? ZFS? What is your usecase for mounting it via fstab? In general I would use a line with simple space -> /dev/sdd /mnt/ssd03 ext4 default 0 0

Have you also checked the real iops on the server itself when your VM hangs? In my opionion you are writing stuff to the RAM which needs to flushed to the storage after a period of time. Until the writing has been finished the IOs will be drastically reduced. You may try to use the whole sysctl...

Have you tried to disable "iothread" at the drives and also cache=default (No cache). This would be my standard where I do get throughput.

I guess that's my issue: Verification is done each month but as counts every second a verification might be already "yellow" if the verification was done 30 days +1 second ago.

You may but you also need to think what is useful for your usecase and what note - simply copy/pasting stuff may not be the best option. Additional can you also share the VM specifications with us?

It's quite simple - just sysctl + the parameter you want to know. sysctl vm.dirty_background_ratio should then post vm.dirty_background_ratio = 5

Have you verified that those sysctl parameters are also being loaded/used by Proxmox?

Have you also tried the sysctl parameters mentioned above?

It says last verify date over 30 days ago but mentions 01-11-2023 00:00:00 - so that would be okay. root@proxmox2:~# proxmox-backup-manager versions --verbose proxmox-backup unknown running kernel: 6.5.11-6-pve proxmox-backup-server 3.1.2-1 running...

I remember that I had similar troubles with Proxmox in the beginning but found this page with this special passage: ## # Adjust vfs cache # https://lonesysadmin.net/2013/12/22/better-linux-disk-caching-performance-vm-dirty_ratio/ # Decriase dirty cache to faster flush on disk...

Which filesystem are you using on the RAID controller?

Verfication config would be: verification: v-49a10228-47a6 ignore-verified true ns outdated-after 30 schedule monthly store Backup

Hello @Chris , my verification job is currently still runing since 0000 hrs - I just copied some from the ongoing log: 2023-12-01T10:43:11+01:00: SKIPPED: verify Backup:vm/109/2023-10-31T18:00:03Z (recently verified) 2023-12-01T10:43:11+01:00: percentage done: 49.28% (11/24 groups, 62/75...

Keep in mind that live restore is also a possibility: While restoring you can already use the VM.

Yes I do: prune: s-953a925f-9901 keep-daily 30 keep-last 60 keep-monthly 12 keep-weekly 4 keep-yearly 4 schedule 2,22:30 store Backup

Hello everyone, I am looking for a configuration which reverifies existing backups of VMs. Currently I am running a verification monthly with "Skip verified" checked but also "Re-Verify after 30 days" enabled. PBS is only verifying new backups and ignoring old ones - even if they have a flag...