public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Christian Ebner <c.ebner@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox] sync: pull: fix regression in resync of corrupt snapshots
Date: Wed, 17 Sep 2025 12:29:57 +0200	[thread overview]
Message-ID: <20250917102957.231963-1-c.ebner@proxmox.com> (raw)

In commit eea1176f ("pull: refactor source snapshot list filtering
logic") the filtering of snapshots to be synced when pulling from the
source datastore was split in preparation for correct pre-filtering
of the snapshot when the verified-only or encrypted-only flags have
been set.

This however introduced a regression, as previously also snapshots
older than the newest snapshot on the target were included in the
list, if the `resync_corrupt` parameter is set and the corresponding
target snapshot failed verification or the loading of the manifest to
check this failed, now however being filtered out unconditionally.

Fix this by keeping these snapshots in the list in case the
`resync_corrupt` flag is set.

Also rename the boolean flag from the incorrect `verified` to
`needs_resync`, in order to reflect the behaviour.

Fixes: eea1176f ("pull: refactor source snapshot list filtering logic")
Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
---
Noted while investigating an unrelated issue.

 src/server/pull.rs | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/src/server/pull.rs b/src/server/pull.rs
index e1c8a7acd..08e6e6b64 100644
--- a/src/server/pull.rs
+++ b/src/server/pull.rs
@@ -676,7 +676,10 @@ async fn pull_group(
     let list: Vec<(BackupDir, bool)> = list
         .into_iter()
         .enumerate()
-        .filter_map(|(pos, (dir, verified))| {
+        .filter_map(|(pos, (dir, needs_resync))| {
+            if params.resync_corrupt && needs_resync {
+                return Some((dir, needs_resync));
+            }
             // Note: the snapshot represented by `last_sync_time` might be missing its backup log
             // or post-backup verification state if those were not yet available during the last
             // sync run, always resync it
@@ -688,7 +691,7 @@ async fn pull_group(
                 transfer_last_skip_info.update(dir.time);
                 return None;
             }
-            Some((dir, verified))
+            Some((dir, needs_resync))
         })
         .collect();
 
-- 
2.47.3



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


             reply	other threads:[~2025-09-17 10:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-17 10:29 Christian Ebner [this message]
2025-09-17 13:41 ` Christian Ebner
2025-09-18  6:45 ` Hannes Laimer

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=20250917102957.231963-1-c.ebner@proxmox.com \
    --to=c.ebner@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