From: Christian Ebner <c.ebner@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: Re: [PATCH proxmox-backup] fix #8003: sync: pull: log skipped chunk reuse for corrupt manifests
Date: Thu, 3 Sep 2026 09:57:16 +0200 [thread overview]
Message-ID: <9906fef3-d9c1-4324-852b-a770b798d24b@proxmox.com> (raw)
In-Reply-To: <20260903075051.109065-1-c.ebner@proxmox.com>
On 9/3/26 9:51 AM, Christian Ebner wrote:
> Chunks from a manifest with verify state failed cannot be re-used
> since it is not known which chunks are corrupt and/or whether the
> index files referenced in the manifest are corrupt. The manifest
> is therefore skipped when determining the chunks from the
> previous snapshot during sync pull jobs. This was however not logged,
> causuing confusion on why a sync job now takes much longer.
>
> Add an additional log line to clarify this.
Fixes: https://bugzilla.proxmox.com/show_bug.cgi?id=8003
> Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
> ---
Forgot the link to the issue, added here for completeness.
prev parent reply other threads:[~2026-09-03 7:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 7:50 [PATCH proxmox-backup] fix #8003: sync: pull: log skipped chunk reuse for corrupt manifests Christian Ebner
2026-09-03 7:57 ` Christian Ebner [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=9906fef3-d9c1-4324-852b-a770b798d24b@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 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.