all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Dietmar Maurer <dietmar@proxmox.com>
To: Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>,
	Dominik Csapak <d.csapak@proxmox.com>
Subject: [pbs-devel] applied: [PATCH proxmox-backup] tape backup: mention groups that were empty
Date: Mon, 9 Aug 2021 09:36:21 +0200	[thread overview]
Message-ID: <c221b391-9c12-2d69-0a9b-d7a74baa0621@proxmox.com> (raw)
In-Reply-To: <20210806093345.2330585-1-d.csapak@proxmox.com>

applied

On 8/6/21 11:33 AM, Dominik Csapak wrote:
> otherwise a user might get a task log like this:
>
> -----
> ...
> found 7 groups
> TASK OK
> -----
>
> which could confuse the users as why there were no snapshots backed up
>
> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
> ---
>   src/api2/tape/backup.rs | 7 ++++++-
>   1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/src/api2/tape/backup.rs b/src/api2/tape/backup.rs
> index 9f815cad..9d1ece40 100644
> --- a/src/api2/tape/backup.rs
> +++ b/src/api2/tape/backup.rs
> @@ -486,11 +486,16 @@ fn backup_worker(
>           let snapshot_list = group.list_backups(&datastore.base_path())?;
>   
>           // filter out unfinished backups
> -        let mut snapshot_list = snapshot_list
> +        let mut snapshot_list: Vec<_> = snapshot_list
>               .into_iter()
>               .filter(|item| item.is_finished())
>               .collect();
>   
> +        if snapshot_list.is_empty() {
> +            task_log!(worker, "group {} was empty", group);
> +            continue;
> +        }
> +
>           BackupInfo::sort_list(&mut snapshot_list, true); // oldest first
>   
>           if latest_only {




      reply	other threads:[~2021-08-09  7:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-06  9:33 [pbs-devel] " Dominik Csapak
2021-08-09  7:36 ` Dietmar Maurer [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=c221b391-9c12-2d69-0a9b-d7a74baa0621@proxmox.com \
    --to=dietmar@proxmox.com \
    --cc=d.csapak@proxmox.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal