Search results

If AutoTrim is enabled on your SSD ZFS pool, try turning it off and reboot your host. zpool autotrim=off yourpool High load due to vdev_autotrim process in "D" state (uninterruptible sleep) autotrim=on ps aux | grep " [RD]" USER PID %CPU %MEM VSZ RSS TTY STAT START TIME...

2023-07-17 10:33:31 CEST Fix will be included with next kernel bump (at max a few weeks). https://bugzilla.proxmox.com/show_bug.cgi?id=4833#c2

I've built the newest pve kernel (6.2.16-3-pve) with the mentioned patch and can confirm that it works, error message is dissapered.

@Neobin Thanks for the hint! I think I am also need to waiting for "Allow a user to push his datastore to a remote server" ;) https://bugzilla.proxmox.com/show_bug.cgi?id=3044

Hi, I've two pbs server, one local and one offsite. On backup the dirty-bitmap status always invalid and cleared. No VM restart, backup mode: snapshot Is this a normal behavior? Backup to Server 1: INFO: Starting Backup of VM 206 (qemu) INFO: Backup started at 2023-06-14 00:36:20 INFO: status...

Thanks for the comment, PR is out. https://github.com/inettgmbh/fail2ban-proxmox-backup-server/pull/8

The Datastore usage is actually the Filesystem usage? It's very confusing, isn't it?

I don't need the space that the actual files consume. I need the space that the whole datastore(s) take up.

ds-1 and ds-2 on a root disc ds-2 and ds-3 on zfs datasets proxmox-backup-manager version --verbose proxmox-backup unknown running kernel: 6.2.11-2-pve proxmox-backup-server 2.4.2-1 running version: 2.4.2 ifupdown2 3.1.0-1+pmx4...

zugehörige Ticket: https://bugzilla.proxmox.com/show_bug.cgi?id=4728 und kommende Änderung in proxmox-sys 0.5.0-1 https://git.proxmox.com/?p=proxmox.git;a=commit;h=ce389914ff79bc99b054c23ae4ca3a487fefe950

If your BIOS is not up to date, try updating it. I had the same problem with Asrock Rack W480D4U motherboard + Intel i7-10700 CPU, after BIOS update the problem is gone.

you can check with systool: apt install sysfsutils systool -c scsi_host -v -d host0 if you have active_mode = "Initiator" and supported_mode = "Initiator" (Initiator Target -> IT) your Controller is in IT-mode. by the way, your log already shows: May 01 13:38:02 Enterprise kernel: mpt2sas_cm0...

Try with following "global_filter": global_filter = [ "r|/dev/zd.*|", "r|/dev/mapper/pve-.*|", "r|/dev/mapper/.*-(vm|base)--[0-9]+--disk--[0-9]+|", "r|/dev/sda|", "r|/dev/sdb|", "r|/dev/sdc|" ] Close the Proxmox GUI in Browser, this can wake up the disks!

Try without "apm". for example:

Es funktioniert bei mir leider nicht.

Ich habe das gleiche Problem mit i7-10700 (Host friert, ohne Log Eintrag, keine Kernel-Panik). Ich habe jetzt Hyper-Threading im Bios ausgeschaltet, mal sehen ob es hilft.

Mit Proxmox 7.3 / Kernel 5.15 schon probiert?

bei mir funktioniert nur mit VirtIO Version 0.1.208: https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.208-1/virtio-win-0.1.208.iso

set/check containter features: Nesting: true FUSE: true check docker storage driver: docker info | grep Storage Storage Driver: fuse-overlayfs

make it executable: chmod +x /usr/local/bin/fuse-overlayfs