From: Dominik Csapak <d.csapak@proxmox.com>
To: "Proxmox Backup Server development discussion"
<pbs-devel@lists.proxmox.com>,
"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup] pull: properly skip missing snapshots
Date: Wed, 27 Nov 2024 10:05:00 +0100 [thread overview]
Message-ID: <e2b7c74d-6c42-4625-b68f-b671d1ef58ea@proxmox.com> (raw)
In-Reply-To: <20241127082604.89880-1-f.gruenbichler@proxmox.com>
Code wise it looks good to me, and tested fine.
I am not sure though if there isn't a slight TOCTOU issue?
if the snapshot is deleted between the exist and verify_state check?
(not sure if there's a lock anyway here, couldn't tell from the surrounding code)
in that case we could maybe check err for ENOENT (if that's returned?) or returning
a custom Error type that includes that information
aside from that, consider this
Reviewed-by: Dominik Csapak <d.csapak@proxmox.com>
Tested-by: Dominik Csapak <d.csapak@proxmox.com>
On 11/27/24 09:26, Fabian Grünbichler wrote:
> when loading the verification state for a local snapshot, it must first be
> ensured that it actually exists, else the lack of manifest will be interpreted
> as corrupt snapshot triggering a "resync" that is actually a sync of all
> missing snapshots.
>
> Fixes: 0974ddfa17be018f777d6ece90a71bfa8fc130d8 "fix #3786: api: add resync-corrupt option to sync jobs"
>
> Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
> ---
> src/server/pull.rs | 26 ++++++++++++++------------
> 1 file changed, 14 insertions(+), 12 deletions(-)
>
> diff --git a/src/server/pull.rs b/src/server/pull.rs
> index 9abb673ae..361ed0687 100644
> --- a/src/server/pull.rs
> +++ b/src/server/pull.rs
> @@ -551,21 +551,23 @@ async fn pull_group(
> .store
> .backup_dir(target_ns.clone(), dir.clone());
> if let Ok(local_dir) = local_dir {
> - match local_dir.verify_state() {
> - Ok(Some(state)) => {
> - if state == VerifyState::Failed {
> + if local_dir.full_path().exists() {
> + match local_dir.verify_state() {
> + Ok(Some(state)) => {
> + if state == VerifyState::Failed {
> + return Some((dir, true));
> + }
> + }
> + Ok(None) => {
> + // The verify_state item was not found in the manifest, this means the
> + // snapshot is new.
> + }
> + Err(_) => {
> + // There was an error loading the manifest, probably better if we
> + // resync.
> return Some((dir, true));
> }
> }
> - Ok(None) => {
> - // The verify_state item was not found in the manifest, this means the
> - // snapshot is new.
> - }
> - Err(_) => {
> - // There was an error loading the manifest, probably better if we
> - // resync.
> - return Some((dir, true));
> - }
> }
> }
> }
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2024-11-27 9:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 8:26 Fabian Grünbichler
2024-11-27 9:05 ` Dominik Csapak [this message]
2024-11-27 9:17 ` Fabian Grünbichler
2024-11-27 10:46 ` Thomas Lamprecht
2024-11-27 9:05 ` [pbs-devel] applied: " Thomas Lamprecht
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=e2b7c74d-6c42-4625-b68f-b671d1ef58ea@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=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