From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 2C0A31FF136 for ; Mon, 04 May 2026 20:04:12 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id C4106EAD5; Mon, 4 May 2026 20:04:10 +0200 (CEST) From: Thomas Lamprecht To: pbs-devel@lists.proxmox.com, Christian Ebner Subject: applied: [PATCH proxmox-backup] api: backup: cleanup backup group created by benchmark Date: Mon, 4 May 2026 20:03:57 +0200 Message-ID: <177791783507.3062238.18222424139289910756.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260430135931.722979-1-c.ebner@proxmox.com> References: <20260430135931.722979-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: 1777917741245 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.003 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: ERDWK4NWW4DI7AVIIQ45IB7YS7KBFQPJ X-Message-ID-Hash: ERDWK4NWW4DI7AVIIQ45IB7YS7KBFQPJ 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, 30 Apr 2026 15:59:31 +0200, Christian Ebner wrote: > The benchmark creates it's own backup group host/benchmark, failed > however to auto-cleanup the group after itself, because since commit > 23be00a42 ("fix #3336: datastore: remove group if the last snapshot > is removed"), cleanup requires an exclusive lock on the backup group > for destroying it. The backup environment however already holds the > exclusive lock to disallow concurrent backups to the same group. > > [...] Applied, thanks! [1/1] api: backup: cleanup backup group created by benchmark commit: c14464141f54ff6312272e1843abca9783af79c2