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 DF7B11FF136 for ; Mon, 20 Apr 2026 09:44:38 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id BDB6F1F0B2; Mon, 20 Apr 2026 09:44:38 +0200 (CEST) Message-ID: <6156681c-60dc-49fe-b2b9-52191582d3c7@proxmox.com> Date: Mon, 20 Apr 2026 09:44:04 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: superseded: [PATCH proxmox-backup 0/2] fixes #7465: add gc-on-unmount flag To: pbs-devel@lists.proxmox.com References: <20260417112755.136134-1-h.laimer@proxmox.com> Content-Language: en-US From: Hannes Laimer In-Reply-To: <20260417112755.136134-1-h.laimer@proxmox.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1776670961591 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.082 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: YRMHBKRQFZWLOBYP7TTJLTX7W32SHGJE X-Message-ID-Hash: YRMHBKRQFZWLOBYP7TTJLTX7W32SHGJE X-MailFrom: h.laimer@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/pbs-devel/20260420074257.9492-1-h.laimer@proxmox.com/ On 2026-04-17 13:26, Hannes Laimer wrote: > So GC can run before unmount, without this its somewhat complicated to > run gc on a datastore that is configured to auto unmount after jobs > finish. > > > Hannes Laimer (2): > api: datastore: add option to run garbage collection before unmount > ui: datastore: expose gc-on-unmount setting > > src/api2/admin/datastore.rs | 33 +++++++++++++++++++++++++++------ > src/api2/config/datastore.rs | 9 +++++++++ > www/datastore/OptionView.js | 23 +++++++++++++++++++++++ > 3 files changed, 59 insertions(+), 6 deletions(-) >