From: Alexander Zeidler <a.zeidler@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH v4 manager/container/guest-common/docs 0/4] fix #3069: add pbs-entries-max to vzdump.conf
Date: Mon, 11 Sep 2023 13:38:24 +0200 [thread overview]
Message-ID: <8c7a8ecd2177eb665660f91d7a5179a9006afb6e.camel@proxmox.com> (raw)
In-Reply-To: <20230728132858.98806-1-a.zeidler@proxmox.com>
On Fri, 2023-07-28 at 15:28 +0200, Alexander Zeidler wrote:
> Users reported[1] about failing container backups to PBS when having
> a large amount of files in a directory.
>
> proxmox-backup-client has already 'entries-max' implemented. The
> default value prevents out of memory (OOM) situations. Overriding
> this parameter needs at least 'Sys.Modify' permissions.
>
> This patch series makes the new optional performance parameter 'pbs-
> entries-max' available in vzdump and vzdump.conf.
>
> [1] https://bugzilla.proxmox.com/show_bug.cgi?id=3069
>
> Signed-off-by: Alexander Zeidler <a.zeidler@proxmox.com>
Ping. Still applies on master.
next prev parent reply other threads:[~2023-09-11 11:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 13:28 Alexander Zeidler
2023-07-28 13:28 ` [pve-devel] [PATCH v4 manager 1/4] fix #3069: vzdump: add property 'performance: pbs-entries-max=N' Alexander Zeidler
2023-07-28 13:28 ` [pve-devel] [PATCH v4 container 2/4]: fix #3069: vzdump: add 'pbs-entries-max' parameter Alexander Zeidler
2023-07-28 13:28 ` [pve-devel] [PATCH v4 guest-common 3/4] fix #3069: vzdump: schema: add 'pbs-entries-max' property Alexander Zeidler
2023-07-28 13:28 ` [pve-devel] [PATCH v4 docs 4/4] vzdump: mention new parameter 'pbs-entries-max' Alexander Zeidler
2023-09-11 11:38 ` Alexander Zeidler [this message]
2023-09-18 15:05 ` [pve-devel] applied-series: [PATCH v4 manager/container/guest-common/docs 0/4] fix #3069: add pbs-entries-max to vzdump.conf 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=8c7a8ecd2177eb665660f91d7a5179a9006afb6e.camel@proxmox.com \
--to=a.zeidler@proxmox.com \
--cc=pve-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