superseded: [PATCH proxmox-backup 0/2] fix #6990: server: drop verify state on push & pull job

["Jakob Klocker" <j.klocker@proxmox.com>]

Superseded-by: https://lore.proxmox.com/all/20260821111826.299588-1-j.klocker@proxmox.com/T/#u
On Thu Jul 9, 2026 at 2:21 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.
>
> This series drops verify_state on sync so the target is verified
> independently. The state is dropped by default.
>
> Tested (verify_state correctly stripped on target):
>  * Pull, verified source, new content, clean sync
>  * Pull, verified source, existing content, clean sync
>  * Pull, corrupted target, resync-corrupt
>  * Push, verified source (has no corrupt path)
>  * Pull, independently-verified target, clean re-sync - state preserved
>
> Link: https://bugzilla.proxmox.com/show_bug.cgi?id=6990
>
>
> proxmox-backup:
>
> Jakob Klocker (2):
>   fix #6990: server: drop verify state on non-decrypt pull job
>   fix #6990: server: drop verify state on push job
>
>  src/server/pull.rs | 42 ++++++++++++++++++++++++++++--------------
>  src/server/push.rs |  6 ++++++
>  2 files changed, 34 insertions(+), 14 deletions(-)
>
>
> Summary over all repositories:
>   2 files changed, 34 insertions(+), 14 deletions(-)