Search results

The system protects itself from an out of memory condition. So this is fair from my perspective. Their seems to be no automatic loadbalancing in PVE yet. Check if this helps you: https://forum.proxmox.com/threads/load-balancing-and-future-features.54745/#post-371251

What does "zpool list" show you? Anything? Are there later messages in syslog about the nvme based pool? E.g. failures?

It is coming from somewhere. Your memory isn't ECC, so technically it can be part oft what you are seeing.. I think it is unlikely but if everything is out of the game a memcheck might be worth it. Also you can try to detach all disks from that particular mirror and re-attaching them. In...

Write errors could also be a bad memory. Are you using ECC mem?

My physical switch behaves similar if it is running too long without a powercycle. Hence i reboot it every 3 months. Give it a try... Aside that are you using the right network settings, vlans, switches etc?

From my documentation. Maybe it helps Proxmox ZFS In-Place Replace a Disk in a RAIDZ-Pool: # Get Status of the pool sudo zpool status HDD-POOL-RAIDZ3 # pool: HDD-POOL-RAIDZ3 # state: DEGRADED #status: One or more devices could not be used because the label is missing or # invalid...

Pulled this from my notes - but it was a Bios / legacy system. No UEFI: #=========================================== ### For Windows Server 2012R2 # Temporary use e1000, megaraid SAS ### Für Windows 8.1 # temporary use SATA disk and e1000 ## Process: # Boot up # install virtio driver #...

Best rule for virtualization: assign only resources that the VM needs. IMHO your VMs are too big for what they do. Dynamic memory ist great on paper but in reality it adds overhead. Ballooning can also be performance heavy due to swap out operations. So always size to the lower limit! This is...

had a similar issue with my setup and padding overhead. Maybe this helps: https://forum.proxmox.com/threads/unexpected-pool-usage-of-zvol-created-on-raidz3-pool-vs-mirrored-pool.65018/post-293908

FYI all: I have made a large upgrade to the script as explained here: https://forum.proxmox.com/threads/lib-modules-filling-up-hard-drive.39199/post-294457

I don't think it is a LF / CRLF issue - but perhaps some encoding-issue. For whatever reason the [[ is interpreted as an actual command, which of course is wrong. Sadly I can't repair what has happened to your system. But I will refresh the script to make the logic different in order to...

Ouch that is ugly @cglmicro I have never experienced something like this and I am using this script-block for literally years now, on different systems and different linux distributions. The output indicates to me that there is something seriously going wrong in terms of the script execution...

I had some issues in the past where the network stack at some point was overloaded. That issued a TCP zero window and everything went nuts. So I'd recommend to use a "bwlimit" on rsync command and see if that helps. Also check the VM configuration and make sure there are no disk related...

Just an heads up for all that use this script. I have noticed on a longer running system that this script does not necessarily prevent the harddrive from filling up. Situation: In case new kernels get installed but the reboot is not yet issued and the newer kernels and modules do not get...

Disagree. This is what the system tells you from the stats. But one thread does not equal a real core. So technically your math is wrong. Check the WWW to understand the difference between threads (SMT) and real cores. This is a standard misunderstanding IMHO...

There is no concept of threads within guests... This is only a concept of the hardware/host. No this is a misconception. You are not seeing the physical core. It is virtualized. AFAIK even with CPU pass through you don't see logical cores (e.g. threads)

Ignore Threads. Use cores for the thought process. Your machine has 2x16C then. So Max of your desired vcpu is 16 then. If it is 1*16 or 2*8 also depends on your memory configuration (buzzword NUMA). HTH

To shut down VMs the following script sample might help. I did not test it and just have thrown it together ;) #!/bin/bash #option="stop" option="shutdown" for vm in `sudo qm list | awk '{print $1}' | grep -v VMID` do echo "$option VM with ID: $vm" command="sudo qm $vm...

Maybe this helps as well: https://forum.proxmox.com/threads/lib-modules-filling-up-hard-drive.39199/ Cheers

sudo pveupdate sudo pveupgrade This did the trick for me. I am still wondering why my script worked for years and suddenly it did not do it anymore. Thanks for your help.