all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup 2/2] api: datastore: wait for active operations to clear before s3 refresh
Date: Tue, 11 Nov 2025 11:13:14 +0100	[thread overview]
Message-ID: <1762855821.u7yqy491qm.astroid@yuna.none> (raw)
In-Reply-To: <20251104131934.449757-3-c.ebner@proxmox.com>

this one looks mostly okay, but as we actually want the exact same
semantics as with unmounting, we could refactor the whole helper there
to do all of the logic?

e.g., have a `wait_until_operations_done_and_ensure_maintenance_mode`
helper that calls a callback (that does the actual unmounting/refreshing)

On November 4, 2025 2:19 pm, Christian Ebner wrote:
> Currently, the s3 refresh does not take into consideration already
> ongoing active operations, only blocking new ones.
> This will however lead to inconsistencies if there are ongoing read
> or write operations. Therefore, actively wait for ongoing operatioins
> to complete before running the actual refresh.
> If an abort was requested while waiting, clear the maintenance mode as
> well.
> 
> Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
> ---
>  src/api2/admin/datastore.rs | 21 ++++++++++++++++++++-
>  1 file changed, 20 insertions(+), 1 deletion(-)
> 
> diff --git a/src/api2/admin/datastore.rs b/src/api2/admin/datastore.rs
> index 00110119f..a43aad610 100644
> --- a/src/api2/admin/datastore.rs
> +++ b/src/api2/admin/datastore.rs
> @@ -2756,7 +2756,26 @@ pub fn s3_refresh(store: String, rpcenv: &mut dyn RpcEnvironment) -> Result<Valu
>          Some(store.clone()),
>          auth_id.to_string(),
>          to_stdout,
> -        move |_worker| {
> +        move |worker| {
> +            let mut active_operations = task_tracking::get_active_operations(&store)?;
> +            let mut old_status = String::new();
> +            while active_operations.read + active_operations.write > 0 {
> +                if worker.abort_requested() {
> +                    maintenance_mode(&store, None).context("failed to clear maintenance mode")?;
> +                    bail!("aborted by user");
> +                }
> +                let status = format!(
> +                    "cannot refresh contents, {} active read and {} active write operations",
> +                    active_operations.read, active_operations.write
> +                );
> +                if status != old_status {
> +                    info!("{status}");
> +                    old_status = status;
> +                }
> +                std::thread::sleep(std::time::Duration::from_secs(1));
> +                active_operations = task_tracking::get_active_operations(&store)?;
> +            }
> +
>              proxmox_async::runtime::block_on(datastore.s3_refresh())?;
>  
>              maintenance_mode(&store, None).context("failed to clear maintenance mode")
> -- 
> 2.47.3
> 
> 
> 
> _______________________________________________
> pbs-devel mailing list
> pbs-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
> 
> 
> 


_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel


  reply	other threads:[~2025-11-11 10:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-04 13:19 [pbs-devel] [PATCH proxmox-backup 0/2] wait for active operations to finish " Christian Ebner
2025-11-04 13:19 ` [pbs-devel] [PATCH proxmox-backup 1/2] datastore: s3 refresh: set/unset maintenance mode in api handler Christian Ebner
2025-11-11 10:09   ` Fabian Grünbichler
2025-11-11 14:53     ` Christian Ebner
2025-11-04 13:19 ` [pbs-devel] [PATCH proxmox-backup 2/2] api: datastore: wait for active operations to clear before s3 refresh Christian Ebner
2025-11-11 10:13   ` Fabian Grünbichler [this message]
2025-11-12 16:37 ` [pbs-devel] superseded: [PATCH proxmox-backup 0/2] wait for active operations to finish " Christian Ebner

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=1762855821.u7yqy491qm.astroid@yuna.none \
    --to=f.gruenbichler@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