The 152 G is the virtual disk size, given to the virtual guest.
The 58 GB is the space of one (or more, you didn't show us the output of df) filesystem(s).
Often both are coupled and give similar size - but that is not a must.
Examine the...
My way to backup host - I've added this line to cron:
0 2 * * tue,sat tar --exclude='var/lib/vz' --exclude='var/lib/snapd' --exclude='var/lib/apt' --exclude='var/lib/dpkg' -czvf /mnt/data/Backup/proxmox/dump/host.tar.gz /etc /var/lib /home /root...
Extension for Multi-Backup-SW solution on a HA PBS
Many admins learn to like the PBS solution from Proxmox although some practical features still are missing in contrast to Veeam like single file restore to the source filesystem location...
After a lot of head scratching, I figured out how to get two NICs working on mini-PC. One is a 2.5GbE port, which needs driver update to run at 2.5GbE, and the other is a 1GbE port. The two NICs are on two different VLANs as well.
Here's the...
Servus,
es ist die letzen Tage von einem User noch sein "traum" Proxmox VE Server zusammen gestellt worden.
Ich teile deshalb hier seine Auswahl, die Teilweise aus meinem erstern Vorschlag und Anpassungen an seine Bedürfnisse besteht.
Viel Spaß...
In my humble opinion, what you’re seeing is just normal Linux behavior: it may swap idle pages even with free RAM to keep ARC/cache. Personally I’d suggest trying zram (with zram-tools or systemd-zram-generator) instead of disabling swap — it...
Also, note that 192.90 is not a private IP space
https://datatracker.ietf.org/doc/html/rfc1918#:~:text=3. Private Address Space
Blockbridge: Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
You should have installed version 9, not 8.x then!
Try to find hints regarding the crashes in the Journal. If it happened during the previous boot you can look at the end of the relevant journal like this:
journalctl -b -1 -p warning -e
For...
Ok I was able to figure out the issue. The thunderbolt interface.d configuration was the culprit. The old config did not seem to want to work with 9. Checking the page I got the instructions from...
of=/dev/zero ?? better be /dev/null otherwise get the sunglasses
:cool: Interesting random as fast as urandom ... what I saw too on newer cpus you can do same as fast as having cores which was previously only one max and with more processes only...
Yes. Maybe. No. On the same machine as above:
~# dd if=/dev/random of=/dev/null bs=1M count=5000
5000+0 records in
5000+0 records out
5242880000 bytes (5.2 GB, 4.9 GiB) copied, 8.26672 s, 634 MB/s
~# dd if=/dev/urandom of=/dev/null bs=1M...
Yes, that's burned into my own mind too.
But "something" has changed. I can read 5 GB from both devices with the same speed:
~# dd if=/dev/urandom of=/dev/zero bs=1M count=5000
5000+0 records in
5000+0 records out
5242880000 bytes (5.2 GB, 4.9...
Ok, Asche auf mein Haupt. Man sollte halt auch die Guest Tools im GAST-SYSTEM d.h. der VM installieren! Dann funktioniert es. :)
Ich hab es so (miss)verstanden, dass die Guest Tools die Verbindung zum Gast-System herstellen und somit auf dem PC...
There is no "migration" with only three nodes. the "3" in your crush rule refers to how many copies on individual nodes that have to exist in order to have a healthy pg (placement group.) the number of OSDs dont matter in this context- you can...
Well, my whole point in the first post is that the absolute minimum is not a scenario I would like to use.
If you think it will work fine for your use case: go for it! (No sarcasm, I mean it!)
The main purpose of 3rd node is just to avoid split-brain situation and halt everything. VMs could/should hop between the stronger node1 and 2 in case of a failure, the third node therefore ensures the avoidance of split-brain with quorum. If...