public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Christian Ebner <c.ebner@proxmox.com>
To: "Proxmox Backup Server development discussion"
	<pbs-devel@lists.proxmox.com>,
	"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup v2 3/6] api: admin: factor out busy waiting on active operations
Date: Thu, 13 Nov 2025 09:38:00 +0100	[thread overview]
Message-ID: <dc02aba9-0b8e-435f-8972-dd658cda5b76@proxmox.com> (raw)
In-Reply-To: <1763021421.pshnohnxvt.astroid@yuna.none>

On 11/13/25 9:16 AM, Fabian Grünbichler wrote:
> On November 12, 2025 5:36 pm, Christian Ebner wrote:
>> Move the logic to wait on no more active operations on a given
>> datastore into a dedicated helper function, to be reused
>> by s3-refresh.
>>
>> Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
>> ---
>> changes since version 1:
>> - not present in previous version
>>
>>   src/api2/admin/datastore.rs | 54 ++++++++++++++++++++++++++-----------
>>   1 file changed, 38 insertions(+), 16 deletions(-)
>>
>> diff --git a/src/api2/admin/datastore.rs b/src/api2/admin/datastore.rs
>> index 6e66b5cf0..7daccf9fd 100644
>> --- a/src/api2/admin/datastore.rs
>> +++ b/src/api2/admin/datastore.rs
>> @@ -2586,29 +2586,21 @@ fn do_unmount_device(
>>       }
>>       let mount_point = datastore.absolute_path();
>>   
>> -    let mut active_operations = task_tracking::get_active_operations(&datastore.name)?;
>>       let mut old_status = String::new();
>> -    let mut aborted = false;
>> -    while active_operations.read + active_operations.write > 0 {
>> -        if let Some(worker) = worker {
>> -            if worker.abort_requested()
>> -                || expect_maintenance_type(&datastore.name, MaintenanceType::Unmount).is_err()
>> -            {
>> -                aborted = true;
>> -                break;
>> -            }
>> +    let aborted = wait_on_active_operations(
>> +        &datastore.name,
>> +        worker,
>> +        MaintenanceType::Unmount,
>> +        |reads, writes| {
>>               let status = format!(
>> -                "cannot unmount yet, still {} read and {} write operations active",
>> -                active_operations.read, active_operations.write
>> +                "cannot unmount yet, still {reads} read and {writes} write operations active",
>>               );
>>               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(&datastore.name)?;
>> -    }
>> +        },
>> +    )?;
>>   
>>       if aborted || worker.is_some_and(|w| w.abort_requested()) {
>>           let _ = expect_maintenance_type(&datastore.name, MaintenanceType::Unmount)
>> @@ -2725,6 +2717,36 @@ pub async fn s3_refresh(store: String, rpcenv: &mut dyn RpcEnvironment) -> Resul
>>       Ok(json!(upid))
>>   }
>>   
>> +/// Wait for no more active operations on the given datastore.
>> +/// If a worker task context is provided, the given callback will be executed for each busy wait
>> +/// iteration.
>> +///
>> +/// Returns with Ok(true) if the worker was aborted or the expected maintenance mode was not set,
>> +/// Ok(false) if no more operations are active.
>> +fn wait_on_active_operations(
>> +    store: &str,
>> +    worker: Option<&dyn WorkerTaskContext>,
> 
> this can drop the Option, all callers actually run in a worker context..

Right, now I'm wondering why this was an option to begin with in the 
do_unmount_device(), but will drop that for the v3.

> 
>> +    maintenance_expected: MaintenanceType,
>> +    mut status_msg_callback: impl FnMut(i64, i64),
>> +) -> Result<bool, Error> {
>> +    let mut active_operations = task_tracking::get_active_operations(&store)?;
>> +
>> +    while active_operations.read + active_operations.write > 0 {
>> +        if let Some(worker) = worker {
>> +            if worker.abort_requested()
>> +                || expect_maintenance_type(&store, maintenance_expected).is_err()
>> +            {
>> +                return Ok(true);
>> +            }
>> +            status_msg_callback(active_operations.read, active_operations.write);
>> +        }
>> +        std::thread::sleep(std::time::Duration::from_secs(1));
>> +        active_operations = task_tracking::get_active_operations(&store)?;
>> +    }
>> +
>> +    Ok(false)
>> +}
>> +
>>   #[sortable]
>>   const DATASTORE_INFO_SUBDIRS: SubdirMap = &[
>>       (
>> -- 
>> 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
> 
> 



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

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

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-12 16:36 [pbs-devel] [PATCH proxmox-backup v2 0/6] wait for active operations to finish before s3 refresh Christian Ebner
2025-11-12 16:36 ` [pbs-devel] [PATCH proxmox-backup v2 1/6] api: datastore: fix typo in helper function name Christian Ebner
2025-11-12 16:36 ` [pbs-devel] [PATCH proxmox-backup v2 2/6] api: admin: make expected maintenance type helper generic over type Christian Ebner
2025-11-12 16:36 ` [pbs-devel] [PATCH proxmox-backup v2 3/6] api: admin: factor out busy waiting on active operations Christian Ebner
2025-11-13  8:15   ` Fabian Grünbichler
2025-11-13  8:38     ` Christian Ebner [this message]
2025-11-12 16:36 ` [pbs-devel] [PATCH proxmox-backup v2 4/6] api: admin: factor out locking and maintenance mode clearing Christian Ebner
2025-11-13  8:18   ` Fabian Grünbichler
2025-11-13  8:43     ` Christian Ebner
2025-11-13  9:08       ` Fabian Grünbichler
2025-11-13  9:11         ` Christian Ebner
2025-11-12 16:36 ` [pbs-devel] [PATCH proxmox-backup v2 5/6] datastore: s3 refresh: set/unset maintenance mode in api handler Christian Ebner
2025-11-12 16:36 ` [pbs-devel] [PATCH proxmox-backup v2 6/6] api: datastore: wait for active operations to clear before s3 refresh Christian Ebner
2025-11-13  8:15   ` Fabian Grünbichler
2025-11-13  9:03     ` Christian Ebner
2025-11-13  8:20 ` [pbs-devel] partially-applied: [PATCH proxmox-backup v2 0/6] wait for active operations to finish " Fabian Grünbichler
2025-11-13 14:23 ` [pbs-devel] superseded: " 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=dc02aba9-0b8e-435f-8972-dd658cda5b76@proxmox.com \
    --to=c.ebner@proxmox.com \
    --cc=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 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