Search results

No ;-) You posted twice. And I wanted to give a potential reader/replier a chance to realize this before writing an answer which has possibly already been answered over there...

This! It's great to have choices. To make a good decision you need to know the disadvantages in beforehand and in detail.

Never used it with this option in my mind. Although I thankfully recognized that I only need one instance of that script per cluster, so obviously it integrates into PVE :-)

See also https://forum.proxmox.com/threads/connection-error-596.183444/ Btw, "Proxmox VE (Deutsch/German)" is for German support...

Purely guessing: it may be an IP address conflict. Triple check if the IP addresses of all devices are the same as before.

"cv4pve" needs direct access to the ZFS pool and for this reason it is installed on the host. "Zamba" is a normal PVE container, just consuming storage via mount-points - which is absolutely usual and documented. --> https://pve.proxmox.com/pve-docs/chapter-pct.html#pct_mount_points

See also https://forum.proxmox.com/threads/storage-performance-iops-difference.183440/

See also https://forum.proxmox.com/threads/storage-performance-iops-difference.183439/

Nein, eher nicht. Die aktuelle ZFS Version unterstützt Fähigkeiten, die bei dir noch nicht "freigeschaltet" worden sind. Du kanst das erstmal ignorieren. Überprüfe noch einmal die Konfiguration in /etc/pve/storage.cfg . Für einen normalen Pool sollte es so aussehen: zfspool: local-zfs...

As so often: it depends. If I run a company and I my services infrastructure is used in my office to make money and I want that to be possible with ~99.9 percent reliability (that's one workday per year) then I use the better tested subscription repository. For my homelab that is not the case...

Those disks were used earlier? In a "bpool"? I did not read read the tutorial you've mentioned; you may erase them completely by something like "dd if=/dev/null of=/dev/disktobeerased bs=1M state=progress" or read man zpool-labelclear

Probably: yes. If I remember correctly removing a snapshot means to integrate the modified blocks (since the point in time when the snapshot was taken) into one single file. That's plain and simple a slow operation. Problems like like this result in the recommendation to use modern...

Usually it is not a good idea to resurrect a seven years old thread. Instead it is recommended to open a new thread with a new description of the actual problem using current data of the existing setup. Of course you may link back here to establish context. The more actual details you add the...

Aber ist das nicht meistens so? Ich verwende high-level Programme, damit ich die vielen, vielen Details "unten drunter" nicht kennen und nutzen muss. Bleiben wir bei PVE: praktisch alle Funktionen (KVM, Container, ZFS, Ceph, iScsi, Netzwerk usw. usf.) kann ich grundsätzlich per Kommandozeile...

For your next iteration: read about adding a (mirrored) "Special Device". And in your current setup try to verify if L2ARC does actually work the way you want it. Examine the output of zarcsummary for this. See https://openzfs.github.io/openzfs-docs/man/master/1/zarcsummary.1.html (( For my...

Each of those (sub-) projects has its own documentation, usually good ones. Just read it, build one/two/three test-setups and learn how to debug them. Then combine everything to build a usable whole, emulating PVE. Theoretically that's no problem, right? But then there comes the difference...

Nein. Aber die Tücke liegt im Detail :-) Wenn du drei Nodes hast, brauchst du kein Quorum Device! Mir ist gerade nicht ganz klar, ob das QDev in dem Fall "von alleine" den Mund hält, oder ob es hier zu "vier Votes" führt. Du willst jedenfalls immer eine ungerade Gesamtzahl Stimmen ("votes")...

Sure! For teaching/learning/debugging this works great. Example: in my Homelab I have one specific cluster member with 64 GiB Ram and 2 TB local storage for VMs. I was able to create six virtual PVE nodes with 8 GiB Ram each, construct a cluster, add another two virtual 32 GB disks to each of...

Well, I believe handling the hardware storage manage should be done from the host. But you may find a way to run command on the host from a container. Think a stringent configured ssh account which can only run specific enumerated commands like "ssh user@pvehost zfs snapshot...

Nun, ich habe noch niemals LVM (im PVE-Kontext) verwendet..., aber wie soll ein Restore die Größe erkennen? Die Fehlermeldung im ersten Post war ja auch "unable to restore CT - unable to detect disk size - please specify rootfs (size)". Und da das Volume ja vor Beginn des Restore zuerst angelegt...