all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Hannes Laimer <h.laimer@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox-backup v5 3/7] api: admin: trigger sync jobs only on datastore mount
Date: Mon, 21 Jul 2025 13:33:10 +0200	[thread overview]
Message-ID: <20250721113314.59342-5-h.laimer@proxmox.com> (raw)
In-Reply-To: <20250721113314.59342-1-h.laimer@proxmox.com>

Ensure sync jobs are triggered only when the datastore is actually
mounted. If the datastore is already mounted, we don't fail,
but sync jobs should not be re-triggered unnecessarily. This change
prevents redundant sync job execution.

Signed-off-by: Hannes Laimer <h.laimer@proxmox.com>
---
 src/api2/admin/datastore.rs | 13 ++++++++-----
 1 file changed, 8 insertions(+), 5 deletions(-)

diff --git a/src/api2/admin/datastore.rs b/src/api2/admin/datastore.rs
index 843c8126..9e8b5af4 100644
--- a/src/api2/admin/datastore.rs
+++ b/src/api2/admin/datastore.rs
@@ -2440,14 +2440,14 @@ fn setup_mounted_device(datastore: &DataStoreConfig, tmp_mount_path: &str) -> Re
 /// The reason for the randomized device mounting paths is to avoid two tasks trying to mount to
 /// the same path, this is *very* unlikely since the device is only mounted really shortly, but
 /// technically possible.
-pub fn do_mount_device(datastore: DataStoreConfig) -> Result<(), Error> {
+pub fn do_mount_device(datastore: DataStoreConfig) -> Result<bool, Error> {
     if let Some(uuid) = datastore.backing_device.as_ref() {
         if pbs_datastore::get_datastore_mount_status(&datastore) == Some(true) {
             info!(
                 "device is already mounted at '{}'",
                 datastore.absolute_path()
             );
-            return Ok(());
+            return Ok(false);
         }
         let tmp_mount_path = format!(
             "{}/{:x}",
@@ -2492,7 +2492,7 @@ pub fn do_mount_device(datastore: DataStoreConfig) -> Result<(), Error> {
             datastore.name
         )
     }
-    Ok(())
+    Ok(true)
 }
 
 async fn do_sync_jobs(
@@ -2594,14 +2594,17 @@ pub fn mount(store: String, rpcenv: &mut dyn RpcEnvironment) -> Result<Value, Er
         move |_worker| async move {
             let name = datastore.name.clone();
             let log_context = LogContext::current();
-            tokio::task::spawn_blocking(|| {
+            if !tokio::task::spawn_blocking(|| {
                 if let Some(log_context) = log_context {
                     log_context.sync_scope(|| do_mount_device(datastore))
                 } else {
                     do_mount_device(datastore)
                 }
             })
-            .await??;
+            .await??
+            {
+                return Ok(());
+            }
             let Ok((sync_config, _digest)) = pbs_config::sync::config() else {
                 warn!("unable to read sync job config, won't run any sync jobs");
                 return Ok(());
-- 
2.47.2



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


  parent reply	other threads:[~2025-07-21 11:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-21 11:33 [pbs-devel] [PATCH proxmox{, -backup} v5 0/8] trigger sync jobs on mount Hannes Laimer
2025-07-21 11:33 ` [pbs-devel] [PATCH proxmox v5 1/1] pbs-api-types: add run-on-mount flag to SyncJobConfig Hannes Laimer
2025-07-22 14:40   ` [pbs-devel] applied: " Thomas Lamprecht
2025-07-21 11:33 ` [pbs-devel] [PATCH proxmox-backup v5 1/7] api: config: sync: update run-on-mount correctly Hannes Laimer
2025-07-21 11:33 ` [pbs-devel] [PATCH proxmox-backup v5 2/7] api: admin: run configured sync jobs when a datastore is mounted Hannes Laimer
2025-07-21 11:33 ` Hannes Laimer [this message]
2025-07-21 11:33 ` [pbs-devel] [PATCH proxmox-backup v5 4/7] bin: manager: run uuid_mount/mount tasks on the proxy Hannes Laimer
2025-07-21 11:33 ` [pbs-devel] [PATCH proxmox-backup v5 5/7] ui: add run-on-mount checkbox to SyncJob form Hannes Laimer
2025-07-21 11:33 ` [pbs-devel] [PATCH proxmox-backup v5 6/7] ui: add task title for triggering sync jobs Hannes Laimer
2025-07-21 11:33 ` [pbs-devel] [PATCH proxmox-backup v5 7/7] docs: add section about `run-on-mount` sync job flag Hannes Laimer
2025-07-22 17:08 ` [pbs-devel] [PATCH proxmox{, -backup} v5 0/8] trigger sync jobs on mount Christian Ebner
2025-07-22 20:14 ` Thomas Lamprecht
2025-07-22 20:14   ` [pve-devel] " Thomas Lamprecht

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=20250721113314.59342-5-h.laimer@proxmox.com \
    --to=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