From: "Michael Köppl" <m.koeppl@proxmox.com>
To: "Michael Köppl" <m.koeppl@proxmox.com>, pbs-devel@lists.proxmox.com
Subject: Re: [PATCH proxmox-backup v2 0/3] fix #7400: improve handling of corrupted job statefiles
Date: Wed, 25 Mar 2026 17:07:26 +0100 [thread overview]
Message-ID: <DHBZQUUCQJU7.2PW3H0U9WZJTN@proxmox.com> (raw)
In-Reply-To: <20260319110318.70346-1-m.koeppl@proxmox.com>
Superseded-by:
https://lore.proxmox.com/pbs-devel/20260325160617.342295-1-m.koeppl@proxmox.com/T/#t
On Thu Mar 19, 2026 at 12:03 PM CET, Michael Köppl wrote:
> This patch series fixes a problem where an empty or corrupted job state
> file (due to I/O error, abrupt shutdown, ...) would cause API endpoints
> for listing jobs to return an error, breaking the web UI for users
> because they could not view any of their configured jobs of that type.
> It would also cause proxmox-backup-proxy to indefinitely skip the jobs
> until a user manually triggered it to rewrite the statefile.
>
> 1/3 is a preparatory patch that centralizes job statefile loading
> in compute_schedule_status instead of having every handler function
> open the statefile, handle potential errors and then passing the
> JobState to compute_schedule_status.
>
> 2/3 fixes the API layer by catching the load error, logging an error
> message, and returning a default JobScheduleStatus. This ensure the API
> returns the job list, showing the affected job without its last run
> status.
>
> 3/3 updates the scheduler loop inside the proxy to match the behavior of
> a a newly created job, triggering the job at its next internal (which
> then rewrites the statefile).
>
> changes since v1:
> - added preparatory patch 1/3, centralizing the statefile loading before
> adapting the handling of the error case in that centralized place
> (compute_schedule_status). Thanks, Christian for the suggestion!
> - adapted the error message if job statefile loading fails to make clear
> that the default status will be returned as a fallback
>
>
> proxmox-backup:
>
> Michael Köppl (3):
> api: move statefile loading into compute_schedule_status
> fix #7400: api: gracefully handle corrupted job statefiles
> fix #7400: proxy: self-heal corrupted job statefiles
>
> src/api2/admin/datastore.rs | 13 +++----------
> src/api2/admin/prune.rs | 9 +++------
> src/api2/admin/sync.rs | 9 +++------
> src/api2/admin/verify.rs | 9 +++------
> src/api2/tape/backup.rs | 9 +++------
> src/bin/proxmox-backup-proxy.rs | 2 +-
> src/server/jobstate.rs | 17 +++++++++++++++--
> 7 files changed, 31 insertions(+), 37 deletions(-)
>
>
> Summary over all repositories:
> 7 files changed, 31 insertions(+), 37 deletions(-)
prev parent reply other threads:[~2026-03-25 16:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 11:03 Michael Köppl
2026-03-19 11:03 ` [PATCH proxmox-backup v2 1/3] api: move statefile loading into compute_schedule_status Michael Köppl
2026-03-19 11:24 ` Christian Ebner
2026-03-19 14:47 ` Michael Köppl
2026-03-19 15:27 ` Christian Ebner
2026-03-23 12:55 ` Fabian Grünbichler
2026-03-23 15:22 ` Michael Köppl
2026-03-19 11:03 ` [PATCH proxmox-backup v2 2/3] fix #7400: api: gracefully handle corrupted job statefiles Michael Köppl
2026-03-19 11:23 ` Christian Ebner
2026-03-19 11:03 ` [PATCH proxmox-backup v2 3/3] fix #7400: proxy: self-heal " Michael Köppl
2026-03-25 16:07 ` Michael Köppl [this message]
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=DHBZQUUCQJU7.2PW3H0U9WZJTN@proxmox.com \
--to=m.koeppl@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