From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id B53871FF13B for ; Wed, 20 May 2026 04:41:05 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id DA258145F1; Wed, 20 May 2026 04:41:03 +0200 (CEST) From: Thomas Lamprecht To: pbs-devel@lists.proxmox.com, Christian Ebner Subject: partially-applied: [PATCH proxmox{,-backup} v4 0/8] fix sync level updates for chunk store Date: Wed, 20 May 2026 04:40:18 +0200 Message-ID: <177924480520.3422753.3758567942269116443.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260514080458.5677-1-c.ebner@proxmox.com> References: <20260514080458.5677-1-c.ebner@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1779244845430 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.004 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment 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: EEPMA747YQOBVKB6SPR5LP2SPOAV7MBT X-Message-ID-Hash: EEPMA747YQOBVKB6SPR5LP2SPOAV7MBT X-MailFrom: t.lamprecht@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 Thu, 14 May 2026 10:04:49 +0200, Christian Ebner wrote: > Currently the sync level configured for a datastore is only > propagated to the chunk store on first lookup, when the chunk > store instance is created. Updating the sync level in the tuning > options does invalidate the cached datastore entry, does however > not re-instantiate the chunk store, to avoid dropping the locks > acquired via the process locker. This means however the sync level > on the chunk store is not updated. > > [...] Applied the pbs-api-types side here, thanks! [1/1] pbs-api-types: derive FromStr for DatastoreTuning parsing commit: a61b6a8e98f481f48b22502bd5b5b1cb73ea83fa