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 356471FF09F for ; Thu, 03 Sep 2026 09:57:22 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id D97412156A; Thu, 03 Sep 2026 09:57:21 +0200 (CEST) Message-ID: <9906fef3-d9c1-4324-852b-a770b798d24b@proxmox.com> Date: Thu, 3 Sep 2026 09:57:16 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH proxmox-backup] fix #8003: sync: pull: log skipped chunk reuse for corrupt manifests To: pbs-devel@lists.proxmox.com References: <20260903075051.109065-1-c.ebner@proxmox.com> Content-Language: en-US, de-DE From: Christian Ebner In-Reply-To: <20260903075051.109065-1-c.ebner@proxmox.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1788422231876 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.683 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: 5XIUH5QS7SLBJCQEQUVI6LVZPYCMXGFU X-Message-ID-Hash: 5XIUH5QS7SLBJCQEQUVI6LVZPYCMXGFU X-MailFrom: c.ebner@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: 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 > --- Forgot the link to the issue, added here for completeness.