From: Hannes Laimer <h.laimer@proxmox.com>
To: Christian Ebner <c.ebner@proxmox.com>,
Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup 4/7] api: admin: trigger sync jobs only on datastore mount
Date: Thu, 15 May 2025 13:33:41 +0200 [thread overview]
Message-ID: <33b47879-fadf-46f6-94ee-135560cda8e5@proxmox.com> (raw)
In-Reply-To: <618be27b-49fe-4bd5-b980-211ef7d93efc@proxmox.com>
On 2/4/25 15:34, Christian Ebner wrote:
> This patch should rather be placed as preparatory patch before patch 3
> and changes to `do_sync_jobs` directly included in the previous patch.
>
Maybe, but these changes only really make sense in this context. If done
before it would be something like
```
move |_worker| async move {
- do_mount_device(datastore.clone())?;
+ if !do_mount_device(datastore.clone())? {
+ return Ok(());
+ }
}
```
I feel like having this change in the context of where it is needed does
add some value. Especially when one tries to find out later why this was
needed. Having code under the `return Ok(())` is pretty clear in terms
of what it is we try to skip here in some cases. Without I could imagine
being like "th was that good for?", then having to go through the commit
message. IMOH, having the extra context here is better than a possibly
better order. But no hard feelings though, if you'd really like this one
before I'll move it for v2.
> On 1/16/25 07:45, Hannes Laimer wrote:
>> 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 | 10 ++++++----
>> 1 file changed, 6 insertions(+), 4 deletions(-)
>>
>> diff --git a/src/api2/admin/datastore.rs b/src/api2/admin/datastore.rs
>> index 21b58391d..e29ff9b99 100644
>> --- a/src/api2/admin/datastore.rs
>> +++ b/src/api2/admin/datastore.rs
>> @@ -2445,14 +2445,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}",
>> @@ -2497,7 +2497,7 @@ pub fn do_mount_device(datastore:
>> DataStoreConfig) -> Result<(), Error> {
>> datastore.name
>> )
>> }
>> - Ok(())
>> + Ok(true)
>> }
>> async fn do_sync_jobs(
>> @@ -2582,7 +2582,9 @@ pub fn mount(store: String, rpcenv: &mut dyn
>> RpcEnvironment) -> Result<Value, Er
>> auth_id.to_string(),
>> to_stdout,
>> move |_worker| async move {
>> - do_mount_device(datastore.clone())?;
>> + if !do_mount_device(datastore.clone())? {
>> + 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(());
>
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2025-05-15 11:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 6:45 [pbs-devel] [PATCH proxmox/proxmox-backup 0/7] trigger sync jobs on mount Hannes Laimer
2025-01-16 6:45 ` [pbs-devel] [PATCH proxmox 1/7] rest-server: add function that returns a join handle for spawn Hannes Laimer
2025-02-04 14:18 ` Christian Ebner
2025-01-16 6:45 ` [pbs-devel] [PATCH proxmox-backup 2/7] api types: add run-on-mount flag to SyncJobConfig Hannes Laimer
2025-02-04 14:24 ` Christian Ebner
2025-02-28 8:21 ` Hannes Laimer
2025-01-16 6:45 ` [pbs-devel] [PATCH proxmox-backup 3/7] api: admin: run configured sync jobs when a datastore is mounted Hannes Laimer
2025-02-04 14:33 ` Christian Ebner
2025-02-28 8:18 ` Hannes Laimer
2025-02-28 12:13 ` Christian Ebner
2025-01-16 6:45 ` [pbs-devel] [PATCH proxmox-backup 4/7] api: admin: trigger sync jobs only on datastore mount Hannes Laimer
2025-02-04 14:34 ` Christian Ebner
2025-05-15 11:33 ` Hannes Laimer [this message]
2025-05-15 11:45 ` Christian Ebner
2025-01-16 6:45 ` [pbs-devel] [PATCH proxmox-backup 5/7] bin: manager: run uuid_mount/mount tasks on the proxy Hannes Laimer
2025-02-04 14:41 ` Christian Ebner
2025-01-16 6:45 ` [pbs-devel] [PATCH proxmox-backup 6/7] ui: add run-on-mount checkbox to SyncJob form Hannes Laimer
2025-02-04 14:46 ` Christian Ebner
2025-02-28 11:54 ` Hannes Laimer
2025-02-04 15:22 ` Christian Ebner
2025-01-16 6:45 ` [pbs-devel] [PATCH proxmox-backup 7/7] ui: add task title for triggering sync jobs Hannes Laimer
2025-02-04 14:54 ` [pbs-devel] [PATCH proxmox/proxmox-backup 0/7] trigger sync jobs on mount Christian Ebner
2025-02-28 8:22 ` Hannes Laimer
2025-05-15 12:43 ` Hannes Laimer
-- strict thread matches above, loose matches on Subject: below --
2024-12-11 10:40 [pbs-devel] [PATCH proxmox-backup " Hannes Laimer
2024-12-11 10:40 ` [pbs-devel] [PATCH proxmox-backup 4/7] api: admin: trigger sync jobs only on datastore mount 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=33b47879-fadf-46f6-94ee-135560cda8e5@proxmox.com \
--to=h.laimer@proxmox.com \
--cc=c.ebner@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