From: Hannes Laimer <h.laimer@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 2/4] api: datastore: unmount datastore after sync if configured
Date: Tue, 11 Nov 2025 13:24:37 +0100 [thread overview]
Message-ID: <c7984174-041a-46ee-8242-50f5c67836a1@proxmox.com> (raw)
In-Reply-To: <1762862576.vbnms9h8p9.astroid@yuna.none>
On 11/11/25 13:08, Fabian Grünbichler wrote:
> On October 29, 2025 5:01 pm, Hannes Laimer wrote:
>> When a sync job is triggered by the mounting of a datastore, we now check
>> whether it should also be unmounted automatically afterwards. This is only
>> done for jobs triggered by mounting.
>>
>> We do not do this for manually started or scheduled sync jobs, as those
>> run in the proxy process and therefore cannot call the privileged API
>> endpoint for unmounting.
>>
>> The task that starts sync jobs on mount runs in the API process (where the
>> mounting occurs), so in that privileged context, we can also perform the
>> unmounting.
>>
>> Tested-by: Robert Obkircher <r.obkircher@proxmox.com>
>> Signed-off-by: Hannes Laimer <h.laimer@proxmox.com>
>> ---
>> src/api2/admin/datastore.rs | 21 +++++++++++++++++++--
>> 1 file changed, 19 insertions(+), 2 deletions(-)
>>
>> diff --git a/src/api2/admin/datastore.rs b/src/api2/admin/datastore.rs
>> index 643d1694..75122260 100644
>> --- a/src/api2/admin/datastore.rs
>> +++ b/src/api2/admin/datastore.rs
>> @@ -2430,6 +2430,7 @@ pub fn do_mount_device(datastore: DataStoreConfig) -> Result<bool, Error> {
>>
>> async fn do_sync_jobs(
>> jobs_to_run: Vec<SyncJobConfig>,
>> + store: String,
>
> instead of this, the helper could also return
>
can do
>> worker: Arc<WorkerTask>,
>> ) -> Result<(), Error> {
>> let count = jobs_to_run.len();
>> @@ -2442,6 +2443,8 @@ async fn do_sync_jobs(
>> .join(", ")
>> );
>>
>> + let mut unmount_on_done = false;
>> +
>> let client = crate::client_helpers::connect_to_localhost()
>> .context("Failed to connect to localhost for starting sync jobs")?;
>> for (i, job_config) in jobs_to_run.into_iter().enumerate() {
>> @@ -2484,7 +2487,21 @@ async fn do_sync_jobs(
>> }
>> }
>> }
>> + unmount_on_done |= job_config.unmount_on_done.unwrap_or_default();
>> + }
>> + if unmount_on_done {
>
> whether unmounting is necessary/desired, and then the caller could
> handle the unmounting.. or even better, the unmount handling could live
> in the caller entirely, because right now if anything here fails, there
> won't be an unmount..
>
hmm, yes. I guess there is an argument to be made for not keeping it
mounted in case anything goes wrong. I thought about it like that, if
something went wrong somebody will want to look at it. So just leave
everything as when the failure occurred.
>> + match client
>> + .post(
>> + format!("api2/json/admin/datastore/{store}/unmount").as_str(),
>> + None,
>> + )
>> + .await
>> + {
>> + Ok(_) => info!("triggered unmounting successfully"),
>> + Err(err) => warn!("could not unmount: {err}"),
>> + };
>> }
>
> we are already in the privileged api daemon here, so we don't need to
> connect to the proxy which forwards to the privileged api daemon again,
> we can just call the unmount inline directly, right?
>
yes, but I wanted the unmounting task/thread to be owned by the api
process, not this one. The idea was to have this one only trigger stuff
>> +
>> Ok(())
>> }
>>
>> @@ -2566,10 +2583,10 @@ pub fn mount(store: String, rpcenv: &mut dyn RpcEnvironment) -> Result<Value, Er
>> info!("starting {} sync jobs", jobs_to_run.len());
>> let _ = WorkerTask::spawn(
>> "mount-sync-jobs",
>> - Some(store),
>> + Some(store.clone()),
>> auth_id.to_string(),
>> false,
>> - move |worker| async move { do_sync_jobs(jobs_to_run, worker).await },
>> + move |worker| async move { do_sync_jobs(jobs_to_run, store, worker).await },
>> );
>> }
>> Ok(())
>> --
>> 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
next prev parent reply other threads:[~2025-11-11 12:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 16:00 [pbs-devel] [PATCH proxmox{, -backup} v2 0/5] unmount datastores after sync job Hannes Laimer
2025-10-29 16:00 ` [pbs-devel] [PATCH proxmox v2 1/1] pbs-api-types: add 'unmount-on-done' field to sync job config Hannes Laimer
2025-11-11 12:08 ` Fabian Grünbichler
2025-11-11 12:26 ` Hannes Laimer
2025-11-11 13:43 ` Fabian Grünbichler
2025-10-29 16:01 ` [pbs-devel] [PATCH proxmox-backup v2 1/4] api: syncjob: correctly update/delete 'unmount-on-done' field Hannes Laimer
2025-10-29 16:01 ` [pbs-devel] [PATCH proxmox-backup v2 2/4] api: datastore: unmount datastore after sync if configured Hannes Laimer
2025-11-11 12:07 ` Fabian Grünbichler
2025-11-11 12:24 ` Hannes Laimer [this message]
2025-11-11 12:56 ` Fabian Grünbichler
2025-11-11 13:03 ` Hannes Laimer
2025-10-29 16:01 ` [pbs-devel] [PATCH proxmox-backup v2 3/4] ui: add 'unmount-on-done' field to SyncJobEdit window Hannes Laimer
2025-10-29 16:01 ` [pbs-devel] [PATCH proxmox-backup v2 4/4] docs: add section about `unmount-on-done` Hannes Laimer
2025-11-12 12:06 ` [pbs-devel] superseded: [PATCH proxmox{, -backup} v2 0/5] unmount datastores after sync job 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=c7984174-041a-46ee-8242-50f5c67836a1@proxmox.com \
--to=h.laimer@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