Recent content by UdoB

Correct. Both are running in the time sliced fashion and a normal user will be able to use both. But technically in a specific microsecond only one can be running.

Ich glaube die Installations-ISO bietet einen Reparatur-Modus an. Natürlich inklusive ZFS usw.

I have no idea. Personally I would make sure that two to four cores are available even when the largest VM is running. My (possibly wrong, I am no guru) understanding is: you have three VMs with 14 cores. Now if all three have "something" to do only two of them can run at the very same time...

For me there was one additional reason to try pve-ceph: it is extremely easy to setup because everything is integrated in the WebGUI we are already firm with.

Just put a link to the correct post here. --> https://forum.proxmox.com/threads/cross-cluster-migration-should-have-option-to-automatically-re-vmid-to-range-config-on-target-cluster.179140/

Dass sich möglicherweise die Namen der Netzwerkkarten geändert haben, hast du auf dem Schirm? Dann klappt natürlich - ohne manuelle Nacharbeit - erstmal nix mehr. https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Network_Interface_Name_Change

Interesting! Unfortunately I have no idea what happens. Did you install some magic scripts with hidden automatisms? Take a look into the journal. After the fact by simple using journalctl or live on the still-turned-on node in a terminal, running journalctl -f

For an example look at https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie#Ensure_Hostname_Resolves_to_Hosts_IP_Address

While there are some staff members actively supporting this community-forum (thanks for that!) the recommended way to be more visible to the developers is to put it into the official bug tracker: https://bugzilla.proxmox.com/enter_bug.cgi?product=pve Please cross-link from there to here and...

Setze "swappiness" auf Null. https://pve.proxmox.com/wiki/ZFS_on_Linux#zfs_swap - auf derselben Seite wie bereits oben verlinkt. Allerdings würde ich das nicht machen, sondern eine kleine Menge präsent lassen. Das basiert lediglich auf meiner persönlichen Wahrnehmung. Ärgerlicherweise kann...

Der "übliche Verdächtige" ist natürlich der ZFS ARC. Der belegte "früher" per Default bis zu 50% des RAM. Und da der ARC zwar schrumpfen kann, dies aber nur sehr langsam funktioniert, kam es dann gelegentlich zu Engpässen. Der aktuelle Default ist wesentlich kleiner - und man kann das natürlich...

In doubt of the details look into the good ol' man page: man zpool-attach SYNOPSIS zpool attach [-fsw] [-o property=value] pool device new_device ... If the existing device is a mirror or plain device (e.g. specified as "sda" or "mirror-7"), the new device will be mirrored...

That's "old behavior", running up to version 8.4 Upgrade to a current version (read: 9.x) and the information shown should get updated on every boot.

It is especially the technical readability of the data chunks from the physical disk which is confirmed by this process. (And then to be sure that the read data is actually correct the checksum is used.)

First: if it fulfills your requirements then it is absolutely fine. But: you are exchanging performance for other features. For me these are important and you have dropped them: technically cheap snapshots, transparent compression, guaranteed integrity - including self-healing and bitrot...