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 99E1C1FF13F for ; Fri, 24 Apr 2026 00:44:41 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 386743259; Fri, 24 Apr 2026 00:44:41 +0200 (CEST) From: Thomas Lamprecht To: pbs-devel@lists.proxmox.com, Hannes Laimer Subject: applied: [PATCH proxmox-backup v8 00/13] fixes #6195: add support for moving groups and namespaces Date: Fri, 24 Apr 2026 00:38:11 +0200 Message-ID: <177698386728.726567.11620419590194139855.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260422133951.192862-1-h.laimer@proxmox.com> References: <20260422133951.192862-1-h.laimer@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: 1776984157886 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.123 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: SNH5LI6FJSGGRCPP76YZXNQMIF7X6KXI X-Message-ID-Hash: SNH5LI6FJSGGRCPP76YZXNQMIF7X6KXI 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 Wed, 22 Apr 2026 15:39:38 +0200, Hannes Laimer wrote: > Add support for moving backup groups and entire namespace subtrees to > a different location within the same datastore. > > Groups are moved with exclusive per-group and per-snapshot locking. > For S3, objects are copied to the target prefix before deleting the > source. Namespace moves process groups individually, deferring and > retrying lock conflicts once, so partially failed moves can be > completed with move-group. > > [...] Applied, thanks! Squashed in the relatively trivial fixes for what Michael found, but I really could not find any issue with locking after multiple looks, so either that came from some side effect in testing or we'd need more info for a good reproducer. [01/13] ui: show empty groups commit: f3cc03637f70a938808ccb20edbc9def1254a16e [02/13] datastore: lift check_namespace_depth_limit to pbs-datastore commit: 650204594b49107578ccfb595cfa2a95ac53a02c [03/13] datastore: have BackupGroup::destroy consume the group lock commit: e9196f3260cb9fc1637af0cdd07a1d9dd551baf2 [04/13] datastore: split remove_namespace into flat and recursive variants commit: 0e21312aff8caf20addc074067457d4f01e296e5 [05/13] datastore: add move journal for coordinating with gc phase 1 commit: a02cad5e602b9ac23a3e06ff4b7294bed8ac9089 [06/13] datastore: add move-group commit: 303917ccd7f3f65491807ab34c661879f4d7f2bf [07/13] datastore: add move-namespace commit: e2d8f1e87e005b7a3d98d1b5d2f4222db0a9cc64 [08/13] docs: add section on moving namespaces and groups commit: 4f8e1c9cc7437473665a283b7a4e5a2fa6e9b2ef [09/13] api: add POST endpoint for move-group commit: 1182f0b0976d6b23e205c89af60979ba84168e78 [10/13] api: add POST endpoint for move-namespace commit: 2b8f5044ec74cb108180ba4f438aee9953baf337 [11/13] ui: add move group action commit: 20ee63d174f736f0da6e4b672b14d3b5e6b9715a [12/13] ui: add move namespace action commit: aa3983e0685ddede540b7b64fb496c67e59a7a06 [13/13] cli: add move-namespace and move-group commands commit: 4d74e20dc03cafa2c5978bb8d9e3edff7131872c