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 B3F0E1FF146 for ; Tue, 26 May 2026 14:32:57 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id BAF861D645; Tue, 26 May 2026 14:32:56 +0200 (CEST) From: Thomas Lamprecht To: pbs-devel@lists.proxmox.com, Christian Ebner Subject: applied: [PATCH proxmox{,-backup} v4 0/8] fix sync level updates for chunk store Date: Tue, 26 May 2026 14:32:42 +0200 Message-ID: <177979860132.2079565.7966614194382049720.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: 1779798748288 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.120 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 KAM_LOTSOFHASH 0.25 Emails with lots of hash-like gibberish 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: LZJZWQAUP4MVZOZZWNMZFODWLRB3FCGA X-Message-ID-Hash: LZJZWQAUP4MVZOZZWNMZFODWLRB3FCGA 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, thanks! [1/7] datastore: GC: avoid double parsing of datastore tuning options commit: b4ccd8c1f759a82adead24131bd0689d6eaaa2c4 [2/7] pbs-config/datastore: add common helper for parsing tuning options commit: 2bd83b632b26289aa517a642679106f6dc263086 [3/7] datastore: restrict chunk store mutex scope to crate only commit: b061003c5ac68482419c4ee9c2453dd5953215d7 [4/7] datastore: avoid useless double borrowing of datastore commit: 2053bbef74d8c341ff7a37f2427139092918e003 [5/7] datastore: move try_ensure_sync_level() implementation to chunk store commit: e90c674b9097c199a3dabad944b7ac72aa8e38d9 [6/7] datastore: fix sync level update propagation to chunk store commit: 893f58876b72273ca71c44378e97c6e137918b35 [7/7] chunk store: include filesystem backing path in log output commit: b334868dec0d759ba769d0c04d04a3964c477416