From: Fiona Ebner <f.ebner@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH manager 07/19] vzdump: stop all running backup jobs of the node
Date: Fri, 6 Nov 2026 15:48:33 +0100 [thread overview]
Message-ID: <ed916980-4367-4280-a149-63bca4776b7e@proxmox.com> (raw)
In-Reply-To: <20261101225849.884587-8-t.lamprecht@proxmox.com>
Am 01.11.26 um 11:59 PM schrieb Thomas Lamprecht:
> @@ -1566,26 +1561,26 @@ sub verify_vzdump_parameters {
> }
>
> sub stop_running_backups {
> - my ($self) = @_;
> + my $nodename = PVE::INotify::nodename();
>
> - my $upid = PVE::Tools::file_read_firstline($pidfile);
> - return if !$upid;
> + my $running = [];
> + for my $worker (PVE::RPCEnvironment::get()->active_workers()->@*) {
> + my $task = PVE::Tools::upid_decode($worker->{upid}, 1) or next;
Nit: could use PVE::UPID
> + next if $task->{type} ne 'vzdump' || $task->{node} ne $nodename;
> + next if !PVE::ProcFSTools::check_process_running($task->{pid}, $task->{pstart});
>
> - my $task = PVE::Tools::upid_decode($upid);
> + # the whole process group, like stopping the task does
> + kill(15, -$task->{pid});
> + push $running->@*, $task;
> + }
>
> - if (
> - PVE::ProcFSTools::check_process_running($task->{pid}, $task->{pstart})
> - && PVE::ProcFSTools::read_proc_starttime($task->{pid}) == $task->{pstart}
> - ) {
> - kill(15, $task->{pid});
> - # wait max 15 seconds to shut down (else, do nothing for now)
> - my $i;
> - for ($i = 15; $i > 0; $i--) {
> - last if !PVE::ProcFSTools::check_process_running(($task->{pid}, $task->{pstart}));
> - sleep(1);
> - }
> - die "stopping backup process $task->{pid} failed\n" if $i == 0;
> + for (1 .. 15) {
> + $running = [grep { PVE::ProcFSTools::check_process_running($_->{pid}, $_->{pstart}) }
> + $running->@*];
> + return if !scalar($running->@*);
> + sleep(1);
> }
> + die "stopping backup process " . join(', ', map { $_->{pid} } $running->@*) . " failed\n";
Nit: could say "process(es)" or conditionally use singular/plural
> }
>
> sub get_included_guests {
next prev parent reply other threads:[~2026-11-06 14:48 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-01 22:58 [PATCH cluster,storage,guest-common,container,manager,docs 00/19] parallel guest backups and backup concurrency limits Thomas Lamprecht
2026-11-01 22:58 ` [PATCH cluster 01/19] datacenter config: add backup concurrency setting Thomas Lamprecht
2026-11-01 22:58 ` [PATCH cluster 02/19] datacenter config: backup concurrency: add cluster-wide limit Thomas Lamprecht
2026-11-01 22:58 ` [PATCH storage 03/19] add backup concurrency option to storages Thomas Lamprecht
2026-11-01 22:58 ` [PATCH guest-common 04/19] vzdump: add options for parallel guest backups and overlapping jobs Thomas Lamprecht
2026-11-01 22:58 ` [PATCH container 05/19] vzdump: honor bandwidth limit for backups to Proxmox Backup Server Thomas Lamprecht
2026-11-06 10:28 ` applied: " Fiona Ebner
2026-11-01 22:58 ` [PATCH manager 06/19] vzdump: notification: capture guest logs right after each backup Thomas Lamprecht
2026-11-06 14:49 ` Fiona Ebner
2026-11-01 22:58 ` [PATCH manager 07/19] vzdump: stop all running backup jobs of the node Thomas Lamprecht
2026-11-06 14:48 ` Fiona Ebner [this message]
2026-11-01 22:58 ` [PATCH manager 08/19] vzdump: show the error if a job could not get the global lock Thomas Lamprecht
2026-11-01 22:58 ` [PATCH manager 09/19] vzdump: run job-init hook and set up target once the job may start Thomas Lamprecht
2026-11-06 14:48 ` Fiona Ebner
2026-11-01 22:58 ` [PATCH manager 10/19] vzdump: list guests as skipped if the job could not start Thomas Lamprecht
2026-11-01 22:58 ` [PATCH manager 11/19] vzdump: back up guests of a job in parallel Thomas Lamprecht
2026-11-06 14:49 ` Fiona Ebner
2026-11-01 22:58 ` [PATCH manager 12/19] vzdump: allow jobs to run alongside each other Thomas Lamprecht
2026-11-06 14:49 ` Fiona Ebner
2026-11-01 22:58 ` [PATCH manager 13/19] ui: options: add backup concurrency for datacenter and nodes Thomas Lamprecht
2026-11-01 22:58 ` [PATCH manager 14/19] ui: backup job: add concurrency and overlap options Thomas Lamprecht
2026-11-01 22:58 ` [PATCH manager 15/19] vzdump: limit concurrent guest backups cluster-wide Thomas Lamprecht
2026-11-06 14:49 ` Fiona Ebner
2026-11-01 22:58 ` [PATCH manager 16/19] vzdump: honor backup concurrency limits of storages Thomas Lamprecht
2026-11-01 22:58 ` [PATCH manager 17/19] api: backup info: add endpoints for cluster-wide backup slots Thomas Lamprecht
2026-11-01 22:58 ` [PATCH manager 18/19] ui: add cluster-wide and storage backup concurrency limits Thomas Lamprecht
2026-11-01 22:58 ` [PATCH docs 19/19] vzdump: document concurrent backups and their limits 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=ed916980-4367-4280-a149-63bca4776b7e@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@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