Am 28/07/2023 um 15:28 schrieb Alexander Zeidler: > 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.zeid...@proxmox.com> > --- > Changes since v3: > * apply Fiona's comments. For details see patch emails. > > Changes since v2: > * apply Fiona's comments. For details see patch emails. > * add new commit (pve-docs) > * update coverletter text > > Changes since v1: > * apply Fiona's comments. For details see patch emails. > > > pve-manager: > Alexander Zeidler (1): > fix #3069: vzdump: add property 'performance: pbs-entries-max=N' > > configs/vzdump.conf | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > > pve-container: > Alexander Zeidler (1): > fix #3069: vzdump: add 'pbs-entries-max' parameter > > src/PVE/VZDump/LXC.pm | 6 ++++++ > 1 file changed, 6 insertions(+) > > > pve-guest-common: > Alexander Zeidler (1): > fix #3069: vzdump: schema: add 'pbs-entries-max' property > > src/PVE/VZDump/Common.pm | 9 +++++++++ > 1 file changed, 9 insertions(+) > > > pve-docs: > Alexander Zeidler (1): > vzdump: mention new parameter 'pbs-entries-max' > > vzdump.adoc | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) >
applied series, thanks! _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
