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 6E8821FF13B for ; Wed, 11 Mar 2026 16:15:09 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id B7B8E3062B; Wed, 11 Mar 2026 16:15:04 +0100 (CET) Message-ID: Date: Wed, 11 Mar 2026 16:15:00 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: superseded: [pbs-devel] [PATCH proxmox-backup v3 0/3] fixes #6195: add support for moving namespaces To: pbs-devel@lists.proxmox.com References: <20250911094943.34300-1-h.laimer@proxmox.com> Content-Language: en-US From: Hannes Laimer In-Reply-To: <20250911094943.34300-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: 1773242066014 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.068 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: EI6ARJV36QLH7D3EEAZLLBDFZSBX4ESH X-Message-ID-Hash: EI6ARJV36QLH7D3EEAZLLBDFZSBX4ESH 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/20260311151315.133637-1-h.laimer@proxmox.com/T/#t On 2025-09-11 11:50, Hannes Laimer wrote: > Adds support for moving namespaces within a datastore. > - we don't create non-existing target namespaces > - we don't allow moving if a namespace with the same "name" already > exists. So given: > /a/b/c/x > /1/2/3/4/x > moving /1/2/3/4/x to /a/b/c/ is not allowed. > these are the only real restrictions. Of course moving itself into > sub-namespaces, exeeding depth limit or moving root are also not. But > those are not really artificial. > > v3, thanks @Thomas: > - add commit message outlining how moving is done > - add some comments containing a simple example that show how paths are > manipulated throughout the moving process > - add short section to docs > > v2, thanks @Shannon: > - only allow moving if no tasks are running, some more info on the > patch itself > > Hannes Laimer (3): > fix #6195: api: datastore: add endpoint for moving namespaces > fix #6195: ui: add button/window for moving a namespace > docs: add section for moving datastores > > docs/storage.rst | 20 ++++- > pbs-datastore/src/datastore.rs | 129 +++++++++++++++++++++++++++++++++ > src/api2/admin/namespace.rs | 50 ++++++++++++- > www/Makefile | 1 + > www/datastore/Content.js | 38 ++++++++++ > www/window/NamespaceMove.js | 47 ++++++++++++ > 6 files changed, 282 insertions(+), 3 deletions(-) > create mode 100644 www/window/NamespaceMove.js >