public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Christian Ebner <c.ebner@proxmox.com>
To: Hannes Laimer <h.laimer@proxmox.com>, pbs-devel@lists.proxmox.com
Subject: Re: [PATCH proxmox-backup v7 2/9] datastore: add move-group
Date: Wed, 22 Apr 2026 10:40:54 +0200	[thread overview]
Message-ID: <84cfe249-23bf-4498-90e1-90b44dd944b2@proxmox.com> (raw)
In-Reply-To: <20260416171830.266553-3-h.laimer@proxmox.com>

On 4/16/26 7:18 PM, Hannes Laimer wrote:
> Add support for moving a single backup group to a different namespace
> within the same datastore.
> 
> For the filesystem backend each snapshot directory is renamed
> individually. For S3 all objects are copied to the target prefix
> before deleting the source, per snapshot.
> 
> Exclusive locks on the group and all its snapshots are acquired
> before the move to ensure no concurrent operations are active.
> Snapshots are locked and moved in batches to avoid exhausting file
> descriptors on groups with many snapshots.

Unless I overlook it, there currently is still one major issue which can 
lead to data loss with this:

Garbage collection uses the Datastore's list_index_files() method to 
collect all index files at the start of phase 1. This is to know which 
chunks need atime updates to mark them as in use. Snapshots which 
disappear in the mean time can be ignored, as the chunks may then no 
longer be in use. Snapshots created in the mean time are safe, as there 
it is the cutoff time protecting newly written chunks which are not 
referenced by any of the index files which are now not in the list.

But if the move happens after GC started and collected the index files, 
but before reaching that index files. the moved index file still might 
reference chunks which are in-use, but now never get an atime update.

Locking unfortunately does not protect against this.

So if there is an ongoing garbage collection phase 1, there is the need 
for some mechanism to re-inject the index files in the list of indices 
and therefore chunks to process.
This might require to write the moved indices to a file, so they can be 
read and processed at the end of GC phase 1 even if GC is running in a 
different process. And it requires to flock that file and wait for it to 
become available before continuing.

> 
> If the target group already exists and merging is enabled, the
> individual snapshots are moved into the existing target group
> provided both groups have the same owner and the source snapshots
> are strictly newer than the target snapshots.
> 
> Signed-off-by: Hannes Laimer <h.laimer@proxmox.com>
> ---

[..]




  parent reply	other threads:[~2026-04-22  8:40 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-16 17:18 [PATCH proxmox-backup v7 0/9] fixes #6195: add support for moving groups and namespaces Hannes Laimer
2026-04-16 17:18 ` [PATCH proxmox-backup v7 1/9] ui: show empty groups Hannes Laimer
2026-04-16 17:18 ` [PATCH proxmox-backup v7 2/9] datastore: add move-group Hannes Laimer
2026-04-20 14:49   ` Fabian Grünbichler
2026-04-21 10:43     ` Hannes Laimer
2026-04-22  8:40   ` Christian Ebner [this message]
2026-04-22  9:07     ` Fabian Grünbichler
2026-04-22  9:24       ` Christian Ebner
2026-04-22  9:25       ` Hannes Laimer
2026-04-22  9:30         ` Christian Ebner
2026-04-22 10:05           ` Fabian Grünbichler
2026-04-22 10:17             ` Hannes Laimer
2026-04-22 10:23               ` Christian Ebner
2026-04-22 10:26                 ` Christian Ebner
2026-04-22 10:32                 ` Hannes Laimer
2026-04-22 11:11                   ` Hannes Laimer
2026-04-16 17:18 ` [PATCH proxmox-backup v7 3/9] datastore: add move-namespace Hannes Laimer
2026-04-20 14:49   ` Fabian Grünbichler
2026-04-16 17:18 ` [PATCH proxmox-backup v7 4/9] docs: add section on moving namespaces and groups Hannes Laimer
2026-04-16 17:18 ` [PATCH proxmox-backup v7 5/9] api: add POST endpoint for move-group Hannes Laimer
2026-04-20 14:49   ` Fabian Grünbichler
2026-04-16 17:18 ` [PATCH proxmox-backup v7 6/9] api: add POST endpoint for move-namespace Hannes Laimer
2026-04-16 17:18 ` [PATCH proxmox-backup v7 7/9] ui: add move group action Hannes Laimer
2026-04-16 17:18 ` [PATCH proxmox-backup v7 8/9] ui: add move namespace action Hannes Laimer
2026-04-16 17:18 ` [PATCH proxmox-backup v7 9/9] cli: add move-namespace and move-group commands Hannes Laimer
2026-04-20 15:02 ` [PATCH proxmox-backup v7 0/9] fixes #6195: add support for moving groups and namespaces Fabian Grünbichler
2026-04-22 13:41 ` superseded: " 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=84cfe249-23bf-4498-90e1-90b44dd944b2@proxmox.com \
    --to=c.ebner@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal