From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id 081931FF0AA for ; Tue, 22 Sep 2026 15:13:54 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id BAB3021480; Tue, 22 Sep 2026 15:13:53 +0200 (CEST) Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Tue, 22 Sep 2026 15:13:49 +0200 Message-Id: Subject: superseded: [PATCH proxmox-backup v2 0/3] fix #6990: server: drop verify state on push & pull job From: "Jakob Klocker" To: "Jakob Klocker" , X-Mailer: aerc 0.20.0 References: <20260821111826.299588-1-j.klocker@proxmox.com> In-Reply-To: <20260821111826.299588-1-j.klocker@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1790082829869 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.464 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: GB2CXHDCVQN56FMVOJFNDXYKZBAHWBWQ X-Message-ID-Hash: GB2CXHDCVQN56FMVOJFNDXYKZBAHWBWQ X-MailFrom: j.klocker@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox Backup Server development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: superseded-by: https://lore.proxmox.com/all/20260922131110.313302-1-j.klock= er@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]