Search results

  1. R

    Relay to Mailservers based on TO: Email-Addr

    I don't use PMG, just wanted to evaluate if should try it. But without that ability i see no reason to switch from standard postfix + postfix-admin to pmg. Basically postfix-admin does that via mapping. Cheers :-)
  2. R

    Relay to Mailservers based on TO: Email-Addr

    Yeah indeed, i wrote non understandable crap :) What i meant was: rama@golima.de -> Kerio stoiko@golima.de -> Exchange lama@golima.de -> Zimbra Routing to Mailserver based on destination email address. Not Domain based. All users are under the se domain. Thanks stoiko :)
  3. R

    ZFS Datastore on PBS - ZFS Recordsize/Dedup...

    Lets do a conclusion, because this thread get too long: Local Storage / PVE Default Settings (Zstd 1thread): ZSTD -> 1GB/s limit LZO -> Around 600MB/s GZIP -> Around 40MB/s none -> 4,5-5 GB/s Local Storage / Zstd: 32 threads + Pigz: ZSTD -> 1GB/s limit LZO -> Didn't tested, but i don't expect...
  4. R

    [SOLVED] Force delete of "Pending removals"

    #!/bin/bash base_dir="/datasets/Backup-HDD-SAS/.chunks/" yesterday=$(date --date="yesterday" '+%Y-%m-%d %H:%M') total_dirs=$(find "$base_dir" -mindepth 1 -maxdepth 1 -type d | wc -l) echo "Total directories to process: $total_dirs" processed=0 find "$base_dir" -mindepth 1 -maxdepth 1 -type d...
  5. R

    ZFS Datastore on PBS - ZFS Recordsize/Dedup...

    https://bugzilla.proxmox.com/show_bug.cgi?id=5481 Im not completely sure if it's SSL, but almost nothing else is left. I cannot break the barrier of 1GB/s, no matter which hardware. And im absolutely sure, that no one can, if the destination is a PBS. Alternative way that's left, is to ditch...
  6. R

    [SOLVED] [iperf3 speed] Same Node vs 2 Nodes (Found a Bug)

    iperf3 -c 172.17.1.131 -P4 Connecting to host 172.17.1.131, port 5201 [ 5] local 172.17.1.132 port 48106 connected to 172.17.1.131 port 5201 [ 7] local 172.17.1.132 port 48108 connected to 172.17.1.131 port 5201 [ 9] local 172.17.1.132 port 48114 connected to 172.17.1.131 port 5201 [ 11]...
  7. R

    [SOLVED] [iperf3 speed] Same Node vs 2 Nodes (Found a Bug)

    Okay, im further in my research, there seems indeed some bug: If i do an iperf3 test from LXC to Node directly: [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 4.44 GBytes 37.9 Gbits/sec 0 434 KBytes [ 5] 1.00-2.00 sec 4.33 GBytes...
  8. R

    [SOLVED] NVME disk "Available Spare" problem.

    Glad god you didn't listened to me xD
  9. R

    Worse performance with higher specs server

    PS: i forgot to mention: echo "performance" | tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor Should increase fsync twice. Thats a dirty hack, but makes it a lot more reliable to test one server against another. Because with ondemand you don't know at which frequency your test was...
  10. R

    ZFS Datastore on PBS - ZFS Recordsize/Dedup...

    Okay, its not ZSTD itself, but a Bug in Proxmox somewhere: https://pve.proxmox.com/pve-docs/chapter-vzdump.html#vzdump_configuration you can set "zstd: 1" I did a test to backup to Local-Storage and indeed zstd runs with 32 Threads!!!! But the Backup-Speeds still hits all the same limits! No...
  11. R

    ZFS Datastore on PBS - ZFS Recordsize/Dedup...

    Actually, lets think different, i can use no Compression, because the files gets anyway Compressed with LZ4 on the Backup-Server, at least via ZFS. But this is still a bummer. That means simply that 1GB/s is the max Backup-Speed Limit for everyone, that don't disable Compression. Cheers EDIT...
  12. R

    ZFS Datastore on PBS - ZFS Recordsize/Dedup...

    Anyone here reached higher Backup-Speed as 800MB/s or 1GB/s ? Maybe thats some sort of PBS limit Its getting weirder! I have created a VM with PBS on another Genoa Server, the measured write speed is 1,5GB/s inside the VM and read around 5GB/s. But thats a ZVOL issue, that im aware of, the...
  13. R

    ZFS Datastore on PBS - ZFS Recordsize/Dedup...

    Lets start with basic tuning parameters that i use: -o ashift=12 \ -O special_small_blocks=128k \ -O xattr=sa \ -O dnodesize=auto \ -O recordsize=1M \ Thats means logbias is default (latency) + special vdev Testings: logbias=latency + special vdev: INFO: Finished Backup of VM 166...
  14. R

    [SOLVED] Force delete of "Pending removals"

    Thats still the only way to delete stupid chunck files, if you need to, lol However, that command will loop through all files and individually touch them, which is a big loop and execution time of touch comes into play either. I have a better idea, to speed that crap up by at least a factor of...
  15. R

    [SOLVED] NVME disk "Available Spare" problem.

    All Samsung Consumer "NVME" drives are pure crap. The sata versions like the 870 Evo/plus are pretty good tho. (in reliability, not iops) But other Brands can be even worse, or better in TBW but with less speed/worse latency. So thats why im using myself something like 970/980/990 Pros/Evos xD...
  16. R

    ZFS Datastore on PBS - ZFS Recordsize/Dedup...

    -> I checked with a script that does: dd if=/dev/zero of=/mnt/$diskid/1m_test bs=1M count=8000 oflag=direct the write speeds for each disk. -> all disks support 4k Locical Block-Size and 512b, but they come shipped by default with 512b. ---> There is absolutely no performance difference between...
  17. R

    Proxmox problem with memory limits in ARC (ZFS)

    zpool status pool: HDD_Z2 state: ONLINE scan: scrub repaired 0B in 06:17:32 with 0 errors on Sun May 12 06:41:33 2024 config: NAME STATE READ WRITE CKSUM HDD_Z2 ONLINE 0...
  18. R

    Warnung

    https://forum.proxmox.com/threads/wrmsr-messages-on-proxmox-8-1.138145/
  19. R

    PVE und HPE Proliant DL380 Gen 9, speziell Sensoren

    War doch das gleiche spiel damals mit darkmode. Solange das Script immer geupdated/angepasst wird auf neue PVE Versionen, passts ja. Die 2 Daten die ausgetauscht werden, sind ja auch kein problem, werden doch eh von PVE ersetzt beim update. Einzige was bedenkenswert ist, ist sensors-detect im...
  20. R

    PVE und HPE Proliant DL380 Gen 9, speziell Sensoren

    Das ist ja gigantisch! Hoffentlich wird das integriert in Proxmox direkt genauso wie der darkmode damals, das ist ne absolut wahnsinns Erweiterung. Jedesmal ins ILO/IPMI/IBMC zu schauen um Temperaturen zu erfahren und die scheiss Management interface sind so kake lahm, aktualisieren eine...