public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Fabian Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied: [PATCH storage 1/3] prune: introduce keep-all option
Date: Mon, 23 Nov 2020 15:58:03 +0100	[thread overview]
Message-ID: <c889f44d-d82e-3ada-9dcb-e8cfdd8a96c0@proxmox.com> (raw)
In-Reply-To: <20201123123310.13898-1-f.ebner@proxmox.com>

On 23.11.20 13:33, Fabian Ebner wrote:
> useful to have an alternative to the old maxfiles = 0. There has to
> be a way for vzdump to distinguish between:
> 1. use the /etc/vzdump.conf default (when no options are configured for the storage)
> 2. use no limit (when keep-all=1)
> 
> Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
> ---
> 
> A mutual dependency bump between storage and manager is needed for this and
> patch #3.
> 
>  PVE/Storage.pm           |  9 ++++++---
>  PVE/Storage/PBSPlugin.pm | 15 +++++++++++----
>  PVE/Storage/Plugin.pm    | 20 +++++++++++++++++++-
>  3 files changed, 36 insertions(+), 8 deletions(-)
> 
>

applied, thanks!




      parent reply	other threads:[~2020-11-23 14:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-23 12:33 [pve-devel] " Fabian Ebner
2020-11-23 12:33 ` [pve-devel] [PATCH storage 2/3] convert maxfiles to prune_backups when reading the storage configuration Fabian Ebner
2020-11-23 14:58   ` [pve-devel] applied: " Thomas Lamprecht
2020-11-23 12:33 ` [pve-devel] [PATCH manager 3/3] vzdump: adapt to new keep-all prune option Fabian Ebner
2020-11-23 14:58 ` Thomas Lamprecht [this message]

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=c889f44d-d82e-3ada-9dcb-e8cfdd8a96c0@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=f.ebner@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal