all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pbs-devel@lists.proxmox.com, Hannes Laimer <h.laimer@proxmox.com>
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	[thread overview]
Message-ID: <177698386728.726567.11620419590194139855.b4-ty@b4> (raw)
In-Reply-To: <20260422133951.192862-1-h.laimer@proxmox.com>

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




  parent reply	other threads:[~2026-04-23 22:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-22 13:39 [PATCH proxmox-backup v8 00/13] fixes #6195: add support for moving groups and namespaces Hannes Laimer
2026-04-22 13:39 ` [PATCH proxmox-backup v8 01/13] ui: show empty groups Hannes Laimer
2026-04-22 13:39 ` [PATCH proxmox-backup v8 02/13] datastore: lift check_namespace_depth_limit to pbs-datastore Hannes Laimer
2026-04-22 13:39 ` [PATCH proxmox-backup v8 03/13] datastore: have BackupGroup::destroy consume the group lock Hannes Laimer
2026-04-22 13:39 ` [PATCH proxmox-backup v8 04/13] datastore: split remove_namespace into flat and recursive variants Hannes Laimer
2026-04-22 13:39 ` [PATCH proxmox-backup v8 05/13] datastore: add move journal for coordinating with gc phase 1 Hannes Laimer
2026-04-22 13:39 ` [PATCH proxmox-backup v8 06/13] datastore: add move-group Hannes Laimer
2026-04-22 13:39 ` [PATCH proxmox-backup v8 07/13] datastore: add move-namespace Hannes Laimer
2026-04-22 13:39 ` [PATCH proxmox-backup v8 08/13] docs: add section on moving namespaces and groups Hannes Laimer
2026-04-22 13:39 ` [PATCH proxmox-backup v8 09/13] api: add POST endpoint for move-group Hannes Laimer
2026-04-22 13:39 ` [PATCH proxmox-backup v8 10/13] api: add POST endpoint for move-namespace Hannes Laimer
2026-04-22 13:39 ` [PATCH proxmox-backup v8 11/13] ui: add move group action Hannes Laimer
2026-04-23 13:35   ` Michael Köppl
2026-04-23 13:47     ` Hannes Laimer
2026-04-22 13:39 ` [PATCH proxmox-backup v8 12/13] ui: add move namespace action Hannes Laimer
2026-04-23 14:49   ` Michael Köppl
2026-04-22 13:39 ` [PATCH proxmox-backup v8 13/13] cli: add move-namespace and move-group commands Hannes Laimer
2026-04-23 16:29 ` [PATCH proxmox-backup v8 00/13] fixes #6195: add support for moving groups and namespaces Michael Köppl
2026-04-23 22:38 ` Thomas Lamprecht [this message]
2026-04-24  8:31   ` applied: " Fabian Grünbichler
2026-04-24  8:43     ` Hannes Laimer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=177698386728.726567.11620419590194139855.b4-ty@b4 \
    --to=t.lamprecht@proxmox.com \
    --cc=h.laimer@proxmox.com \
    --cc=pbs-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal