From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>, dea <dea@corep.it>,
Mark Schouten <mark@tuxis.nl>
Subject: Re: [pbs-devel] Scheduler causing connectivity issues?
Date: Mon, 18 Jul 2022 15:30:53 +0200 [thread overview]
Message-ID: <facb2f53-ab61-5f24-fe3c-ad50232f7a00@proxmox.com> (raw)
In-Reply-To: <26375c15-9c68-df28-707f-3e19fb903451@corep.it>
Am 17/07/2022 um 17:04 schrieb dea:
>
> after upgrade to 2.2-4 connection problem persist:
FYI, there's proxmox-backup-server version 2.2.5-1, it includes a stop gap [0] for
an issue that could be the one affecting your system, the difference between the
previous improvements is that this doesn't necessarily has to stem from a system
with high load (IO pressure).
It's sadly hard to create a synthetic reproducer and thus also hard to know for sure
that this one addresses the regression in the various environments PBS runs in, so
we'd appreciate feedback on that.
That package is available on pbstest as of now.
[0]: https://git.proxmox.com/?p=proxmox-backup.git;a=commitdiff;h=c2206e21e0f27fbb7610180fc9dc3cb2fe1c4c16
cheers,
Thomas
next prev parent reply other threads:[~2022-07-18 13:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 15:49 Mark Schouten
2022-07-08 7:09 ` Thomas Lamprecht
2022-07-08 9:36 ` Jorge Boncompte
2022-07-08 9:40 ` dea
2022-07-11 8:44 ` Mark Schouten
2022-07-13 7:55 ` dea
2022-07-13 8:14 ` Thomas Lamprecht
2022-07-13 10:41 ` Mark Schouten
2022-07-15 11:49 ` Thomas Lamprecht
2022-07-15 12:01 ` dea
2022-07-15 12:57 ` Thomas Lamprecht
2022-07-15 13:02 ` dea
2022-07-15 13:24 ` dea
2022-07-15 14:43 ` dea
2022-07-17 15:04 ` dea
2022-07-18 13:30 ` Thomas Lamprecht [this message]
2022-07-19 11:01 ` David Lawley
2022-07-19 13:04 ` Thomas Lamprecht
2022-07-19 15:08 ` dea
2022-07-18 7:31 ` Mark Schouten
2022-07-18 11:03 ` Thomas Lamprecht
2022-07-20 7:30 ` Mark Schouten
2022-07-21 13:10 ` Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=facb2f53-ab61-5f24-fe3c-ad50232f7a00@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=dea@corep.it \
--cc=mark@tuxis.nl \
--cc=pbs-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox