From: "Jakob Klocker" <j.klocker@proxmox.com>
To: "Jakob Klocker" <j.klocker@proxmox.com>, <pbs-devel@lists.proxmox.com>
Subject: superseded: [PATCH proxmox-backup v2 0/3] fix #6990: server: drop verify state on push & pull job
Date: Tue, 22 Sep 2026 15:13:49 +0200 [thread overview]
Message-ID: <DLLVEJAGX8WJ.TP0G4HOGMUEB@proxmox.com> (raw)
In-Reply-To: <20260821111826.299588-1-j.klocker@proxmox.com>
superseded-by: https://lore.proxmox.com/all/20260922131110.313302-1-j.klocker@proxmox.com/T/#u
On Fri Aug 21, 2026 at 1:18 PM CEST, Jakob Klocker wrote:
> When syncing a snapshot to another datastore, the source's verify_state
> is currently carried over to the target. This reports the target
> snapshot as verified even though its stored copy was never checked
> there. Since verify jobs skip snapshots that already carry a
> verify_state, the target's copy can't be verified again.
>
> Chunks are checksummed in memory while being transferred, but a verify
> serves a different purpose: confirming the write to the (external)
> target actually succeeded.
> [SNIP]
prev parent reply other threads:[~2026-09-22 13:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 11:18 [PATCH proxmox-backup v2 0/3] fix #6990: server: drop verify state on push & pull job Jakob Klocker
2026-08-21 11:18 ` [PATCH proxmox-backup v2 1/3] server: pull: run blocking file operations on the blocking pool Jakob Klocker
2026-08-28 10:30 ` Christian Ebner
2026-09-03 12:57 ` Jakob Klocker
2026-08-21 11:18 ` [PATCH proxmox-backup v2 2/3] fix #6990: server: drop verify state on push job Jakob Klocker
2026-08-28 10:30 ` Christian Ebner
2026-08-21 11:18 ` [PATCH proxmox-backup v2 3/3] fix #6990: server: drop verify state on non-decrypt pull job Jakob Klocker
2026-08-28 11:11 ` Christian Ebner
2026-09-03 13:59 ` Jakob Klocker
2026-09-04 7:32 ` Christian Ebner
2026-09-22 13:13 ` Jakob Klocker [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=DLLVEJAGX8WJ.TP0G4HOGMUEB@proxmox.com \
--to=j.klocker@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