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 v2 4/6] api: admin: factor out locking and maintenance mode clearing
Date: Thu, 13 Nov 2025 09:18:42 +0100 [thread overview]
Message-ID: <1763021452.3pvb2jf8os.astroid@yuna.none> (raw)
In-Reply-To: <20251112163624.691139-5-c.ebner@proxmox.com>
On November 12, 2025 5:36 pm, Christian Ebner wrote:
> Provide a helper which allows to either clear the maintenance mode if
> the worker was aborted, or call the provided callback while holding
> the datastore config lock.
>
> In preparation for reusing the same logic for the 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 | 50 +++++++++++++++++++++++++------------
> 1 file changed, 34 insertions(+), 16 deletions(-)
>
> diff --git a/src/api2/admin/datastore.rs b/src/api2/admin/datastore.rs
> index 7daccf9fd..8d58b5059 100644
> --- a/src/api2/admin/datastore.rs
> +++ b/src/api2/admin/datastore.rs
> @@ -2584,7 +2584,6 @@ fn do_unmount_device(
> if datastore.backing_device.is_none() {
> bail!("can't unmount non-removable datastore");
> }
> - let mount_point = datastore.absolute_path();
>
> let mut old_status = String::new();
> let aborted = wait_on_active_operations(
> @@ -2602,21 +2601,14 @@ fn do_unmount_device(
> },
> )?;
>
> - if aborted || worker.is_some_and(|w| w.abort_requested()) {
> - let _ = expect_maintenance_type(&datastore.name, MaintenanceType::Unmount)
> - .inspect_err(|e| warn!("maintenance mode was not as expected: {e}"))
> - .and_then(|(lock, config)| {
> - unset_maintenance(lock, config)
> - .inspect_err(|e| warn!("could not reset maintenance mode: {e}"))
> - });
> - bail!("aborted, due to user request");
> - } else {
> - let (lock, config) = expect_maintenance_type(&datastore.name, MaintenanceType::Unmount)?;
> - crate::tools::disks::unmount_by_mountpoint(Path::new(&mount_point))?;
> - unset_maintenance(lock, config)
> - .map_err(|e| format_err!("could not reset maintenance mode: {e}"))?;
> - }
> - Ok(())
> + let mount_point = datastore.absolute_path();
> + clear_or_run_maintenance_locked(
> + &datastore.name,
> + worker,
> + MaintenanceType::Unmount,
> + aborted,
> + || crate::tools::disks::unmount_by_mountpoint(Path::new(&mount_point)),
> + )
> }
>
> #[api(
> @@ -2747,6 +2739,32 @@ fn wait_on_active_operations(
> Ok(false)
> }
>
> +// Either clear the current maintenance mode if the worker was aborted or run the provided callback
> +// while keeping the datastore config lock, so the mode cannot be altered. Clears the maintenance
> +// mode after successful callback execution.
> +fn clear_or_run_maintenance_locked(
> + store: &str,
> + worker: Option<&dyn WorkerTaskContext>,
this can also drop the Option ;)
but given that we now have two helpers with two almost identical call
sites, could we not make it a single helper?
e.g., `run_maintenance_locked` that
- waits for operations to finish while checking worker status and
maintenance type (with status updates via a passed in format string or
callback)
- obtains the lock
- runs the actual maintenance task via a provided closure/callback/..
- clears the maintenance mode and drops the lock
> + maintenance_expected: MaintenanceType,
> + aborted: bool,
> + callback: impl Fn() -> Result<(), Error>,
> +) -> Result<(), Error> {
> + if aborted || worker.is_some_and(|w| w.abort_requested()) {
> + let _ = expect_maintenance_type(store, maintenance_expected)
> + .inspect_err(|e| warn!("maintenance mode was not as expected: {e}"))
> + .and_then(|(lock, config)| {
> + unset_maintenance(lock, config)
> + .inspect_err(|e| warn!("could not reset maintenance mode: {e}"))
> + });
> + bail!("aborted, due to user request");
> + } else {
> + let (lock, config) = expect_maintenance_type(store, maintenance_expected)?;
> + callback()?;
> + unset_maintenance(lock, config)
> + .map_err(|e| format_err!("could not reset maintenance mode: {e}"))
> + }
> +}
> +
> #[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
next prev parent reply other threads:[~2025-11-13 8:18 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
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 [this message]
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=1763021452.3pvb2jf8os.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox