Search results

As posted link, it's a bug with glibc and zfs sparse

https://forum.proxmox.com/threads/proxmox-ve-9-0-iso-upload-corrupts-some-windows-server-2025-isos.169531/

Have you read the CLI example : https://forum.proxmox.com/threads/feature-request-advanced-restore-options-in-gui.109707/post-747788

Since PVE 8.1 , clean install set ARC Max size to 10% of physical memory , max to 16 GiB : https://pve.proxmox.com/wiki/ZFS_on_Linux#sysadmin_zfs_limit_memory_usage Existing installation require manual edit : To permanently change the ARC limits to 16 GiB add (or change if already present) the...

What about this ip ?

post your /etc/network/interfaces

is using Masquerading NAT ? if yes, don't forget additionnal iptables rule PREROUTING -i fwbr+ ... --zone 1 https://pve.proxmox.com/wiki/Network_Configuration

it's expected as tcdump show all packets on the interface, dropped or not.

@P=P Have you read previous posts ?

Again, don't conclude something without facts. Compromised VM cannot access host, that's the point of the virtualization. Reinstalling host isn't required. Check journalctl/eventlog of VM/VPS/VDS perhaps there is just a simple shutdown. Here is forum for Proxmox side only. Virtualizor overlay...

As said, it's only bots which try credentials. Not worry, if you have robust password. As SSH on port 22 is the most used, providers enable "Fail2ban" to mitigate attempts, but nowadays bots has many other ip to continue the job. As said, only whitelisting access by ip or vpn can prevent these...

What does that mean ? You need to post facts, like real messages, logs or errors. it's expected that firewall show scan and login attempts to exposed hosts. it's doesn't mean an attack. No, I mean self hosted vpn. it's another way, instead self hosted vpn, you can allow only specified ip (only...

That will not solve the problem which is your cheap disks, just delay a bit more. I doubt that should enough to mitigate these bad disks for ZFS, perhaps more effective for the WD Red model, but as many posts said : ZFS require enterprise flash disks + striped mirror for best write performance.

How do you conclude that ? BTW, first recommendation is : do not expose publicly PVE. Use firewall to whitelist ip or vpn.

As it's written , it's unsafe for VM, not only if power cut , but also if OOM killer or Physical Hard Reset. CrystalDiskMark, by default, benchs 1 GB of data, which remains in cache, data doesn't hit disk , try with 32 GB and problem should persist. Servers grade disables disk's write cache as...

As always, it depends, many GB daily written indeed require DC drives. But, if not ZFS, regular SSD is often enough for PBS as only new data is written, because existing data is never re written.

The point is the context where you have the issue !

hw raid model ? raid type ? how many disk ? ssd model ?

from/to another computer ? direct connection ?

These are not suitable at all. Even without ZFS they writes slow after short duration.