das ist das greylisting feature von PMG - siehe die Dokumentation:
https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmgconfig_mailproxy_greylisting
die mail sollte dann beim naechsten zustellversuch einfach angenommen werden.
bei manchen...
Raid set auto-scrubs would not match data vs parity if you got corruption on a disk - so the ctrl would know and you would be able to read the events and logs - but would only be useful auto-repairable in raid6 config as in raid5 the parity would...
Hi!
Thanks for your work. I FULLY agree with you!
For about 20 years, all my customers’ OSs have run on top of HPE RAID controller logical drives, and I have NEVER LOST a single bit/file/block.
About 5 years ago I started using Proxmox (new...
DE2000H is an old low cost external ha-raid storage system (with very old Netapp E-series ctrl's, tech spec max 3GB/s read seq, max 100k/r + 35k/w iops) and you are running it in raid5 as mentioned. Assuming you run iSCSI in 10 and not 1Gbit mode...
Hi everyone,
I’m seeing a strange CPU scheduling/load balancing behavior with Proxmox VE 9.1 on Windows Server 2022 Terminal Server VMs.
Environment:
Proxmox VE 9.1
AMD EPYC 9375F hosts
Windows Server 2022 RDS/Terminal Server VMs
Multiple VMs...
Off-topic: sorry, seems that "spoiler" doesn't preserve the formatting, so CODE is better.
I'm not asking you to edit your posts, just informing for future :cool:.
As for the LVM issue: I'm afraid of giving some harmful advice, so don't proceed...
Hi @Chytris, I submitted a bug here (https://bugzilla.proxmox.com/show_bug.cgi?id=7572) please add your observations, problem still happening with latest kernel 6.17.13-6-pve
Hi @a.vaccaro,
yes, please upgrade, the issue should be fixed in qemu-server >= 9.1.5 with commits:
551c0078 ("fix #6935: vmstatus: use CGroup for host memory usage")
61d76518 ("vm status: guard get_memory_stat() call with eval")
Hi Onslow, here are the output:
As was likely mentioned around the same time as your post, all configuration for this device has "disappeared." However, it is still present at `/etc/lvm/backup/micron5100`.
Greetings
Felix
Heya
To my understanding, OVS will let me use a single bridge for all vlans.
This way I can configure the vlan tag on the VMs themself.
However, all guides add "tag=X". Which is not what I want. It should just do all vlans.
I can't find what...
Welcome, @FelixZ
If it's possible, could you edit your post and place those commands and their outputs in CODE blocks?
I mean this icon in the menu: "< / >".
Or even better: place long outputs in "SPOILER" blocks (icon of a crossed eye)...
AFAIK "Normally" your system should show both (logs & filename) in the configured host's time zone.
In the GUI, what have you set in; <node>,Time,Time zone ?
If you wish to have all in UTC, just set it to that.