Search results

Yes. And yes. It has been discussed so many times... I won't repeat the arguments. Yes. I must admin that in my Homelab all of my NVMe lack PLP (while nearly all SSDs have it). For my $Dayjob cluster I would never do so. Yes, NVMe has a much higher IOPS (and bandwidth) than SATA, but the...

Das ist zwar in englischer Sprache, aber da musst du durch: https://pmg.proxmox.com/wiki/index.php/Upgrade_from_8_to_9#Preconditions https://pmg.proxmox.com/wiki/index.php/Upgrade_from_8_to_9#Update_the_configured_APT_repositories

If that is your only goal then skip virtualization and install bare metal! If you want to run several VMs then sum up the RAM requirements and add 4 to 8 GiB for the OS and cache. Then double that resulting number ;-) Given that that software requires 16+8 GiB for server+client 32 GiB Ram...

If the respective admin knows these tools (and their possible pitfalls) they will work fine. Both tools are well established and tested. But for a new user of the PVE eco system (with regard to replication) I do highly recommend to stay away from third party apps first. Use the mechanism PVE...

First remove the double entries, mentioned by @janus57 , then: On my PVE's there is only "Ceph Squid" offered in the "Repositories --> Add:Repository" drop-down menu. Maybe you should upgrade from Quincy to Squid - but do so following a guide! (And creating a backup first.)...

Six of them in an additional/second vdev? Yes. This has the advantage of doubling the IOPS of the pool. The disadvantage is that there is no automatic re-balancing (yet). Yes. That's the "classic" approach. It has the advantage to not require additional disks and space to connect them. Since...

There is no state it can inherited. It can only start; it can only boot to then be running again. If a host is dead the VM is too ;-)

That question makes no sense. When a host is powered off a live migration is simply not possible. Live migration requires the source VM to be running! ;-)

I believe this is a myth :-) Let's take a look. I've added a QDev to a four node virtual test-cluster. Normal operation: ~# pvecm status Cluster information ------------------- Name: pn2 Config Version: 5 Transport: knet Secure auth: on Quorum information...

The SLOG will only help with SYNC writes. As far as I know PBS .chunks are written "normal". (Can someone prove me wrong?) And that SLOG will accept incoming data of one single 5 seconds interval while a second TXG (transaction group) is being flushed out to the HDDs. So it stores 10 seconds...

I'm not sure what this is. Maybe RaidZ3? You may show zpool status to show topology information. (Preferable in text form and in ...-tags.) RaidZ/Z2/Z3 can be tricky and may seem to waste a large amount of space. Example...

There are too many options without additional information. Feel free to add some more technical details regarding your system. (Cluster? Server hardware? Mini-PC? Amount of Ram? ECC Ram? HDD? SSD? ZFS? Number of VMs? PCI-passthrough? ... ... ... ) Try to find hints regarding the crashes in...

Ja, bei weitem. https://pve.proxmox.com/wiki/ZFS_on_Linux#sysadmin_zfs_limit_memory_usage : " ... will be set to 10 % of the installed physical memory," - also vielleicht etwas über 3 GiB.

https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Beta_Documentation : "...with the objective of providing a centralized overview of all your individual nodes and clusters. It also enables basic management like migrations of virtual guests without any cluster network requirements." :-)

Perhaps you can find some hints here: https://forum.proxmox.com/threads/fabu-no-network-connectivity-after-installation-or-after-switching-the-router-can-not-load-the-web-gui-in-a-browser.160091/

Look at: Datacenter --> Metric Server --> Add (Button Drop/Down) --> Open Telemetry. Disclaimer: haven't used it yet...

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 partition table from inside the guest and verify...

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 a description of "-b" etc. consult man journalctl...

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 count=5000 5000+0 records in 5000+0 records out...

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 GiB) copied, 8.25407 s, 635 MB/s ~# dd...