public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>
Subject: [pbs-devel] partially-applied: [PATCH proxmox-backup 1/3] sync: fix premature return in snapshot skip filter logic
Date: Mon, 04 Nov 2024 13:15:11 +0100	[thread overview]
Message-ID: <1730722421.eutmwxhuvw.astroid@yuna.none> (raw)
In-Reply-To: <20241104105830.85612-1-c.ebner@proxmox.com>

applied this one!

On November 4, 2024 11:58 am, Christian Ebner wrote:
> While checking which snapshots to sync, the filter logic incorrectly
> included the first snapshot newer that the last synced one
> unconditionally, bypassing the transfer last check for that one
> snapshot. Following snapshots are correctly handled again.
> 
> E.g. of an incorrect sync by excerpt of a task log provided by a user
> in the community forum [0], with transfer last set to 1:
> 
> ```
> skipped: 2 snapshot(s) (2024-09-29T18:00:28Z .. 2024-10-20T18:00:29Z) - older than the newest local snapshot
> skipped: 5 snapshot(s) (2024-10-28T19:00:28Z .. 2024-11-01T19:00:32Z) - due to transfer-last
> sync snapshot vm/110/2024-10-27T19:00:25Z
> ...
> sync snapshot vm/110/2024-11-02T19:00:23Z
> ```
> 
> Not only the last, but the first newer than newest and last were
> incorrectly synced.
> 
> By dropping the early return, leading to incorrect inclusion of the
> snapshot, the transfer last condition is now correctly checked as
> well.
> 
> Link to the issue reported in the community forum:
> [0] https://forum.proxmox.com/threads/156873/
> 
> Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
> ---
>  src/server/pull.rs | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/src/server/pull.rs b/src/server/pull.rs
> index 3117f7d2c..cc1427196 100644
> --- a/src/server/pull.rs
> +++ b/src/server/pull.rs
> @@ -534,7 +534,6 @@ async fn pull_group(
>              } else if already_synced_skip_info.count > 0 {
>                  info!("{already_synced_skip_info}");
>                  already_synced_skip_info.reset();
> -                return true;
>              }
>  
>              if pos < cutoff && last_sync_time != dir.time {
> -- 
> 2.39.5
> 
> 
> 
> _______________________________________________
> pbs-devel mailing list
> pbs-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
> 
> 
> 


_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel


  parent reply	other threads:[~2024-11-04 12:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-04 10:58 [pbs-devel] " Christian Ebner
2024-11-04 10:58 ` [pbs-devel] [PATCH proxmox-backup 2/3] sync: pull: do not resync currently newest snapshot on target Christian Ebner
2024-11-04 12:15   ` Fabian Grünbichler
2024-11-04 12:20     ` Christian Ebner
2024-11-04 10:58 ` [pbs-devel] [PATCH proxmox-backup 3/3] sync: pull: simplify logic for source snapshot filtering Christian Ebner
2024-11-04 12:15   ` Fabian Grünbichler
2024-11-04 12:15 ` Fabian Grünbichler [this message]
2024-11-04 12:57   ` [pbs-devel] partially-applied: [PATCH proxmox-backup 1/3] sync: fix premature return in snapshot skip filter logic Christian Ebner

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=1730722421.eutmwxhuvw.astroid@yuna.none \
    --to=f.gruenbichler@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 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