You have "Streaming: off". Did you test "on"?
I have good success with that turned on - window movement feels much faster. Probably this depends on several factors... and I do not have any benchmarks.
Unfortunately I do not remember pre-conditons or other details...
I believe that term lacks a fixed meaning in PVE context. (Is it Corosync? Migration? Management? What is it?)
For migration you can specify the to-be-used network under Datacenter --> Options --> Migration Settings --> Network
:-)
Although you wrote
I would nevertheless like to mention the official tool "pve-network-interface-pinning" --> https://pve.proxmox.com/wiki/Network_Configuration#_naming_conventions
Ohne sync=1 ist das ganze asynchron - und "normal" im Sinne, dass nur im üblichen 5-Sekunden-Takt geschrieben wird.
Da wird RAM + CPU-Leistung getestet, nicht die NVMe. Aber ja, das ist dann eher "real world" als mit sync=1.
Do you have a specific reason to use this "ancient" release?
If not... please upgrade to (non-subscription):
~# pveversion
pve-manager/9.1.6/71482d1833ded40a (running kernel: 6.17.13-1-pve)
Usually the relevant .iso has been downloaded to (and is stored on) the same PC where I am using the web browser for iDrac on = my local PC.
The whole point of this mechanism is that the .iso is not copied to the server ahead of (boot-) time but used "directly" via iDrac from the disk on my...
A single vdev? That's worst case - there is no way no make it slower than that! (Even a RaidZ3 has the same IOPS = same speed...)
My recommendation would have been 7*mirrors --> seven times the IOPS of that construct...
Sorry, I have no trivial cure for that situation. You may increase the the...
The Quorum Device cannot access the cluster via ssh.
The cluster can access the Quorum Device - until you remove the rights granted during installation: https://forum.proxmox.com/threads/fabu-how-to-setup-a-quorum-device-and-secure-it-by-disabling-root-access.181525/
We did not verify this at that time.
I did it now, a few months later: https://forum.proxmox.com/threads/fabu-how-to-setup-a-quorum-device-and-secure-it-by-disabling-root-access.181525/
Usage of the Quorum Device
It kicks in automatically. Now we got “7” instead of “6” votes = one more than at the beginning:
root@pna:~# pvecm status
...
Votequorum information
----------------------
Expected votes: 7
Highest expected: 7
Total votes: 7
Quorum: 4
Flags...
Statement: it is not required to allow root@cluster to login to a separate “Quorum Device”-machine after installation.
The “tl;dr” boils down to a single line:
~$ echo "PermitRootLogin no" | sudo tee /etc/ssh/sshd_config.d/permitrootlogin.conf
(( This is Debian, and it comes without “sudo” by...
So hätte ich das (als Ceph-Laie) nicht formuliert. Das, was Ceph unbedingt braucht, ist ein schnelles Netz - oder auch zwei. Und zwar idealerweise ein separates. Für mich hört sich das echt nach Storage-Area-Network an ;-)
Vielen Dank für die Anleitung! Ich konnte alles erfolgreich auf meinem "N5 Pro" durchspielen. Zwei kleine Anmerkungen habe ich:
"shaderc" scheint es in meinem 24.04.4 nicht zu geben. Stattdessen hilft:
apt install libshaderc-dev
Und es fehlen zwei Tools:
apt install glslc curl
(Ja, das ist...
I would remove it from the cluster and handle it as "separated" - https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_remove_a_cluster_node
When it is repaired you would need to join the cluster again. Note that this might not be trivial as a new name and a new IP address are recommended -...