I read through the chain, and I dont really understand what everyone is arguing about.
Yes. ceph requires a minimum configuration (network topology, OSD count, etc) before its performant.
this the is the wrong question to ask. whether someone...
You’re running Windows 11 on a CPU from the Windows 7 era. That proves absolutely nothing other than that you can get hardware to do insane things. I can show you a Ceph cluster that does Windows 11 updates in less than 5 minutes on just 10G...
Win11 VM running on Ceph finished the updates sometime between last night and this morning.
I got home from work and rebooted the VM so that said Win11 updates can go into effect.
You can see, from the screenshot below, when I started the...
If you want a technical discussion, you need to do it on technical terms. Your benchmarks (like most benchmarks) are invalid because you're not benchmarking the 'same thing'. Moreover, you're benchmarking 1 thing (Windows?) which, if you know...
PBS packages directly installed on my PVE Host, with a dedicated disk for Backups via Sata.
+ a USB-Drive as external datastore for automated syncing + ejection, when the drives gets connected.
No overhead, for an extra host and still meeting...
Here all PBS install are alongside PVE.
Disk dedicated to PBS datastore.
Single HDD for few VM is enough
vzdump is only good for manual/one shot backup.
For scheduled backups PBS is mandatory.
Speedy and Verify schedule.
Restore is faster since...
Hello Impact thanks for replying,
I had the machine off. I turned it on and no ssh access. I put a monitor and keyboard and i ran: ip a
and it shows no ip address
apt update shows errors indicating it cannot resolve deb.debian.org
apt...
There is a gluster-like replacement and there are others that regularly pop up that run entirely in userspace. Gluster being unstable as per my prior comment is just personal experience. If you do hammer it in real production, it is very likely...
This is a logical fallacy. Just because the security issues you linked are not pressent in an older kernel doesn't mean that your old kernel doesn't have any security issues. In fact it defenitifely will have known (and unknown) security issues...
thanks! the sync of the corosync.conf did work for me on a Proxmox 9.x node which was offline during the addition of 2 other nodes.
Copying the corosync.conf worked well:
scp root@existing-node:/etc/corosync/corosync.conf...
There is a gluster-like replacement and there are others that regularly pop up that run entirely in userspace. Gluster being unstable as per my prior comment is just personal experience. If you do hammer it in real production, it is very likely...
Also NVMe Gehäuse mit NVMe over Fabric haben alle mindesten 100GBit was ja auch kein Problem ist, da kostet ein Switch mit 4x 100G auch nur 800€, aber die Enclosures kosten mehrere Tausend.
Was günstig ist, wären gebrauchte SAS Enclosures, da...
Also NVMe Gehäuse mit NVMe over Fabric haben alle mindesten 100GBit was ja auch kein Problem ist, da kostet ein Switch mit 4x 100G auch nur 800€, aber die Enclosures kosten mehrere Tausend.
Was günstig ist, wären gebrauchte SAS Enclosures, da...
Get an external EFI-Shell binary (for example via "pbatard"'s github repos: https://github.com/pbatard/UEFI-Shell/releases), and put that onto a USB drive into the "/EFI/BOOT/" folder, renamed (the shell bianry) as "bootx64.efi".
See if you can...
Yes, and as CVE-2026-43134, CVE-2026-43284, and CVE-2026-43500 shows, updates are great. [/s]
(i.e. if you didn't update your kernels, then you wouldn't have given yourself these LPE exploits that you otherwise, previously, didn't have.
Same...
Here all PBS install are alongside PVE.
Disk dedicated to PBS datastore.
Single HDD for few VM is enough
vzdump is only good for manual/one shot backup.
For scheduled backups PBS is mandatory.
Speedy and Verify schedule.
Restore is faster since...
My environment does have support for(see attachment for more info)
tx-udp_tnl-segmentation: on
tx-udp_tnl-csum-segmentation: on
but K8S network is not working.
I also tried patching
Rebooted all my Proxmox nodes and it did not solve the issue...
:shrug: dunno if it is time specific.
(I mean, one would only be able to say this, in retrospect. At the time, when it happened, there was little means to know whether it was going to be a (permanent) issue or one that would've been resolved as...