Recent content by Sprinterfreak

This issue is all about PBS failing on high load or small deployments. This issue is also about failing silently for I guess a lot of people who don't have turned on extensive reporting. Bottom line. Fine for You @itNGO when You can afford and/or require fast restore times. But this here also...

Because 14tb SSD's are exactly cheap and widely available. Not. Maybe thats the reason why it is not possible to have the data grave on all flash. I'am glad I could fit all my vm hosts with all flash and even that took ages recently to obtain the drives. Took really multiple cancelled orders...

Should I say, that this is still happening on pbs 3.3.2 and above? I bet it is due to io delay caused by spinning rust seeking to death when multiple cluster nodes hammer the pbs server simultaneously. Some nodes simply time out. This is pretty consistent and always 1 to 2 random nodes in the...

I have just installed a new pbs server with an active-backup bond setup. After creating a new bond interface via UI, the rendered /etc/network/interface confg is missing the bond-miimon 100 parameter, which basically prevents any slave interface from ever become selected. For VE the...

This also affects the installer. Guess what, I am unable to type an = character via the servers remote kvm. So my solution was to grab a keyboard drive to the location where the server is located just to press = on the physical keyboard, so I could do the rest remotely again. Good luck if You're...

After having tested it a while now I can say that valid certificates don't make sense for at least pbs installs. Not only does it need more engineering on the ACME side, it is also not meant to be on the pve side. The whole trust mechanism of proxmox is based on pinned certificate fingerprints...

Hi, also filed an issue https://bugzilla.proxmox.com/show_bug.cgi?id=5719 I did manage to pull a wildcard certificate with the suggested patches to the DNS_NAME_FORMAT schema. There is of course still something weird happening. You need to add two domain entries - the.domain.tld -...

So I'd like to issue a valid LE wildcard certificate for my pbs instance. This is especially useful to hide detailed information behind the public scope of the infrastructure in the LE domain log. I have a working infrastructure for rfc2136 (dns-01) challenge handling through an alias domain...

There are other threads [1] with crash dumps, which narrow down the issue to blk_flush_complete_seq, this in turn calls blk_flush_restore_request. This function has recent activity [2]. Namingly fixing a NULL pointer dereference. As far I can see, this has just been scheduled to be in 6.10-rc1...

I wonder if this has something to do with https://lore.kernel.org/all/20240501110907.96950-9-dlemoal@kernel.org/

I have achieved moving vm's between existing datastores. * create a remote "localhost" * add sync job on the target datastore, pulling from localhost's source datastore with a group filter only covering the desired vm * run-now the sync job, after that remove the temporary sync job...

This is actually what I expected too. Thats why I migrated my kind of important vm's manually over to the second node before first node reboot. I expected the cluster to get read-only (no management input possible) but not to die completely. I also don't have shared ressources within the VM's...

Yes, you seem to be totally right. Fencing really kills the host. There was HA configured on a vm template... Not only that solved, thank's for pointing out the slim qdevice. There is of course a 3rd node in progress but this really is the newly available(?) fix for that. If I remembered right...

TL;DR if one host is rebooted, the second hosts hard-resets. No logs in dmesg/messages. I have a little setup running on ThinkCenters, with nvme formatted as lvm. This setup serves a few home applications and is mainly for educational purposes. A playground so to say. Both hosts have 16GB RAM...

Happened to me today after stopping a manual snapshot task because I forgot to uncheck RAM while it was writing RAM to disk. The vm remained killed and locked. The snapshot also remained in snapshot list but NOW was not shown as child. After `qm unlock`, trying to remove snapshot, resulted in >...