Search results

Hi, I have setup matrix-hookshot to manage Notifications from my Clusters in a way that makes sense. Somehow I am struggling in getting all Information I need to the Messages. Besides the Message and severity I want to have the Hostname that emitted the message, and basically all Data that...

Has this patch merged?

@dcsapak that'd be awesome.

Without the Patch it's simply not usable for 100's of TB to backup, so it would really be nice to have this patch and not be forced to patch manually.

Yeah i tried that: checked out v3.3.2, then I get: Preparing to unpack rust-proxmox-backup-build-deps_3.3.2-1_all.deb ... Unpacking rust-proxmox-backup-build-deps (3.3.2-1) ... Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting...

Yeah well I am forced to checkout v3.3.2 because in the current master the patch won't apply at all because pbs-api-types is missing. root@promox-build:~/proxmox-backup# patch -p1 <../pbs.patch can't find file to patch at input line 5 Perhaps you used the wrong -p or --strip option? The text...

Hi Hannes, yeah: root@promox-build:~/proxmox-backup# apt-get build-dep . Note, using directory '.' to get the build dependencies Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have...

Hello, since the thread patch that adresses this https://forum.proxmox.com/threads/low-zfs-read-performance-disk-tape.139494/ still didn't make it upstream I am forced to maintain my own patched Version of PBS, so I have to build my own debian packages. I usually take a clean bookworm vm for...

Is there any news when the threads parameters will go upstream? It's still pretty much unusable without a self-patched pbs.

You can build yourself the packages, which is a bit clumsy but worked for me. I could send you the .deb files if you trust me, but I would also propose that Proxmox should integrate this upstream.

Firmware on the SAS Controller is up-to-date, tapelib as well. Next I will replace Controller and SAS cable, but i have the feeling this might not be the issue..

May I bump this please? I just replaced my SL3, and the problem persists.

This is exactly what seems weird to me: root@<hostname>:/etc/proxmox-backup# grep yearly prune.cfg |wc -l 0 the complete file: root@<hostname>:/etc/proxmox-backup# cat prune.cfg prune: s-292bacf9-6ca5 keep-daily 30 keep-monthly 6 keep-weekly 8 schedule sat 18:15 store px11...

Hi, I need some clarification about the pruning behaviour of the PBS Server. I usually let the PBS Server do all the pruning to keep permission as restrictive as possible. Essentielly Datastore.Backup is the only Role I need to assign the User. I have a Datastore with 14 daily, 8 weekly and 6...

Is there any ETA when this will make it into a release?

Yeah, i also work around with it through iscsiadm -m node -o delete [..] but it's really really annoying. I know that it#s basically the iscsi vendors wrong implementation, but previously proxmox behaved in a way that it was easy to work around. It would really be good to get a feedback of a...

No worries..

I think this is not related to what's discussed in this Thread.

yeah, but proxmox is not exactly designed for rolling back things. I already thought about just replacing the perl modules manually, but still this is not exactly nice :D

I have community subscriptions but this shouldn't make a difference. Changes in the last Proxmox releases have just broken Multipath support, I don't see why I should need a more expensive subscription. Might be that iSCSI is still in use, but at least Proxmox is treating it legacy'ish? It's...